io.github.raulbr90/changebook

Everything the atlas knows about specific FILES: which module each belongs to, its risk, open regression alerts on those modules, how often they changed recently, the recent commits that touched each file (cite these instead of running git log), and the CURRENT value of watched config constants (with the commit it comes from — no need to re-read the file for those). Call this BEFORE editing a file — one cheap call instead of re-reading the code and its git history. Args: - files (required): 1-8 repo-relative paths. - project (recommended): the repo you are working in (folder name or slug). The atlas is per-project — always scope to your own project. Returns (structured): { files: [{ file, modules: [{ module, risk, changes, last_changed, last_note }], open_alerts, recidivism: [{ module, prior_regressions }], recent_commits: [{ commit, commit_aliases, date }], recent_commits_more, watched_values: [{ name, value, commit }] }] }

Get the change history of one module: what changed, why it matters, the files touched and (when available) a verbatim excerpt of each diff. This is the token-saving alternative to re-reading a module's source: it gives an agent the recent evolution and risk picture in one call. Args: - module (required): exact module name as returned by atlas_modules. - limit (1-20, default 5): number of recent changes to include. - include_excerpts (default true): include diff excerpts (short previews unless full is set). - full (default false): return the diff excerpts verbatim instead of the token-saving previews. Only pass it when you actually need the code lines. - project (recommended): the repo you are working in (folder name or slug). The atlas is per-project — always scope to your own project. Returns (structured): { module, count, changes: [{ date, commit, risk, note, tech, files, business_impact, excerpt, excerpt_truncated }] }. Notes describe the code AS OF their commit/date — verify current values in the code before asserting them.

List the modules of the product as known by ChangeBook, aggregated from the change history. For each module: domain, latest risk level, number of analyzed changes and last-change date. Files, notes and diffs live in atlas_module_detail — this is the map, not the terrain. Args: - domain (optional): filter by domain (e.g. "billing"). - project (recommended): the repo you are working in (folder name or slug). The atlas is per-project — always scope to your own project. Returns (structured): { count, modules: [{ module, domain, risk, changes, last_changed }] }

List the most recent analyzed code changes from the ChangeBook changelog (newest first). Each entry has a business-level impact summary, an optional technical summary, and the modules it touched. Use this to catch up on what changed in the product without re-reading the codebase. Args: - limit (1-50, default 10): entries to return. - offset (default 0): pagination offset. - search (optional): case-insensitive text filter over the business and technical summaries. - project (recommended): the repo you are working in (folder name or slug). The atlas is per-project — always scope to your own project. Returns (structured): { count, offset, has_more, changes: [{ id, date, commit, business_impact, diff_chars, files, files_more, modules: [{ module, risk }] }] }. files is a capped union (files_more = paths cut). Pass include_tech for summary_tech. Don't use for per-module deep dives — use atlas_module_detail for that.