local-review-harness/FIRST_COMMAND_FOR_CLAUDE_CODE.md
Claude (review-harness setup) f3ee4722a8 Phase A + B (MVP) — local review harness
Implements the MVP cutline from the planning artifact:
- Phase A: skeleton + CLI dispatch + provider interface + stub model doctor
- Phase B: scanner + git probe + 12 static analyzers + reporters + pipeline
- Phase B fixtures: clean-repo, insecure-repo, degraded-repo

12 static analyzers per PROMPT.md "Suggested Static Checks For MVP":
hardcoded_paths, shell_execution, raw_sql_interpolation, broad_cors,
secret_patterns, large_files, todo_comments, missing_tests,
env_file_committed, unsafe_file_io, exposed_mutation_endpoint,
hardcoded_local_ip.

Acceptance gates passing:
- B1 (intake produces accurate counts) ✓
- B2 (insecure fixture fires ≥8 distinct check_ids — actually 11/12) ✓
- B3 (clean fixture produces 0 confirmed findings — no false positives) ✓
- B4 (scrum mode produces all 6 required markdown + JSON reports) ✓
- B5 (receipts.json marks degraded phases honestly) ✓
- F  (self-review on this repo runs without crashing) ✓ — exit 66 (degraded
  because Phase C LLM review is hardcoded skipped)

Phases C (LLM review), D (validation cross-check), E (memory + diff +
rules subcommands) deferred per the cutline. The MVP delivers the
evidence-first path; LLM is purely additive.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-30 00:56:02 -05:00

565 B
Executable File

First Command For Claude Code

Read all Markdown files in this directory.

Do not write code yet.

Produce only the following:

  1. Execution plan
  2. Module breakdown
  3. Proposed file structure
  4. Risk register before implementation
  5. MVP cutline
  6. Acceptance gates

Wait for confirmation before coding.

Hard rules:

  • Do not create implementation files yet.
  • Do not install dependencies yet.
  • Do not auto-commit.
  • Do not rewrite the prompt.
  • Do not collapse phases.
  • Do not add cloud dependencies.
  • Do not claim the system works until commands prove it.