This page helps you choose a practical guide. Each guide identifies its runtime dispatcher, commands, and verified surfaces against current source. Open the selected guide and follow that scope.
How to use the catalog
- Start from the job you need to complete.
- Open one primary guide; add a second only when the task truly crosses boundaries.
- Confirm the project, source revision, and read-only diagnostics before mutation.
- Treat generated findings as evidence for the accountable product decision.
- For changes, preserve tests, approval, rollback, and delivery evidence required by your process.
Understand a codebase
| Job | Guide | Expected result |
|---|---|---|
| Establish project context and find the first useful entry points | 01 — Onboarding | A bounded map of relevant modules and symbols |
| Produce or check source-linked documentation | 03 — Documentation | Documentation tied to resolvable code evidence |
| Review module boundaries and dependencies | 11 — Architecture | An architecture finding with an explicit impact zone |
| Trace behavior across registered repositories | 10 — Cross-repository analysis | Repository-qualified paths and unresolved boundary gaps |
| Identify reachable interfaces and attack surface | 16 — Entry points | A checked inventory of exposed entry points |
| Find a repeated structural pattern | Pattern search | Search results separated from any rewrite action |
Security and compliance
| Job | Guide | Expected result |
|---|---|---|
| Inspect security findings without applying fixes | 02 — Security audit | Findings with source locations and severity context |
| Review an explicitly approved security autofix flow | 02 — Security audit autofix | Preview, approval boundary, patch, and verification |
| Run a compliance-oriented engineering check | 08 — Compliance | Evidence gaps and qualified assessment output |
| Investigate a security incident | 14 — Incident response | Scope, affected paths, containment evidence, and follow-up |
Change and review
| Job | Guide | Expected result |
|---|---|---|
| Find the safest placement for a feature | 04 — Feature development | Candidate placement and affected contracts |
| Restructure code without intended behavior change | 05 — Refactoring | Before/after impact, tests, and a keep-or-rollback decision |
| Review a bounded change | 09 — Code review | Findings tied to the exact diff and base revision |
| Plan a repeated API or symbol migration | 13 — Mass refactoring | Explicit match set, preview, and rollback boundary |
| Combine quality, security, and performance checks | 18 — Code optimization | Separate lane results, not one opaque score |
| Check a change against coding standards | 19 — Standards check | Rule-specific findings and verification |
| Compose supported scenario outputs | Composite workflows | Traceable inputs and results for each component |
Diagnose and improve quality
| Job | Guide | Expected result |
|---|---|---|
| Investigate a performance concern | 06 — Performance | A measured hotspot hypothesis and validation plan |
| Find test coverage gaps | 07 — Test coverage | Missing-path evidence and focused test targets |
| Quantify technical-debt candidates | 12 — Technical debt | Prioritized debt items with source evidence |
| Trace an observed failure | 15 — Debugging | Reproduction, candidate path, and verified cause |
| Inspect dependency risk and structure | 20 — Dependencies | Direct/transitive dependency evidence and next action |
Publication boundary
The former file-editing scenario is archived. Use a task-specific guide with preview, authorization, tests, and rollback for the actual change surface.
A scenario result contributes to task closure. Product acceptance combines requirements, executed tests, accountable review, relevant security evidence, and the delivery process used by the installation.