adlc-review

star 1

Review staged or working-tree changes with ADLC context and read-only gate output.

davidvictor By davidvictor schedule Updated 5/20/2026

name: adlc-review description: Review staged or working-tree changes with ADLC context and read-only gate output.

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:

{
  "schema_version": 1,
  "gate": "review",
  "status": "pass|warn|fail",
  "blocking": false,
  "blockers": [],
  "affected_files": [],
  "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.

Install via CLI
npx skills add https://github.com/davidvictor/adlc-skills --skill adlc-review
Repository Details
star Stars 1
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator