Adlc Review

ADLC Review

Use this for correctness, regression, maintainability, and risk review.

Process

1. Resolve effective ADLC paths from .adlc/config.yaml; use adlc resolve-config when the CLI is available.
2. Pin the diff target.
3. Read the active plan, configured rules, and architecture.
4. Review behavior first, then maintainability, security, docs, and release risk.
5. Prefer review-sidecar, security-sidecar, and rules-sidecar for independent read-only checks when available.
6. Classify blockers as autonomous-fixable or human-gated. Code, docs, tests, rules, and security findings should suggest adlc-fix; human-gated blockers are limited to explicit decisions, credentials or external accounts, destructive or production operations, legal/security sign-off, scope or product ambiguity, or user-requested approval points.
7. Lead with blocking findings. Say clearly when there are none.

Output

End with a final parseable adlc-gate-result fenced block:

```adlc-gate-result { "schemaversion": 1, "gate": "review", "status": "pass|warn|fail", "blocking": false, "blockers": [], "affectedfiles": [], "suggested_next": { "command": "adlc-commit|adlc-fix|null", "reason": "Short reason." } }

Use `suggested_next.command: "adlc-fix"` for autonomous-fixable blockers. Use `null` only when a human-gated blocker prevents the next autonomous gate.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [davidvictor](https://github.com/davidvictor)
- **Source:** [davidvictor/adlc-skills](https://github.com/davidvictor/adlc-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.