Codebase Orientation
Map the owners, entry points, contracts and verification paths relevant to a change, with source-backed relationships and explicit unknown coverage.
SPECIALIST PRESET · REVIEW · V0.1.0
Trace a proposed change through real ownership, contracts and dependency boundaries before recommending edits.
From a full checkout. JSON includes file hashes, not an installation or an execution.
node tools/bundle.mjs role architecture-reviewerThese 6 skills are references, not instructions to load everything at once.
Map the owners, entry points, contracts and verification paths relevant to a change, with source-backed relationships and explicit unknown coverage.
Qualify one derived code index against the intended checkout, source bytes, coverage and known query answers before using it for impact decisions.
Use current project/task graphs and semantic navigation to map impact, enforce important boundaries, and validate derived configuration without duplicating existing tooling.
Evolve OpenAPI contracts against an accepted consumer baseline with explicit wire semantics, compatibility analysis, migration decisions, and runtime checks.
Produce evidence-linked technical-debt findings with consequences, deliberate tradeoffs, bounded repair targets and independent reproduction checks rather than a style-driven rewrite list.
Explain an inspected system or change with source-linked relationships, explicit assumptions, readable visual structure and an equivalent accessible narrative.
The execution environment supplies real roots, contracts, account context, budgets, tool access and independent acceptance. Keep those private. Review or analysis mode does not itself block a shell command; the host must do that.
Explore Specialist Role Composition →