prod-debug

prod-debug

Invocation

Two modes:

• /prod-debug — load context and enter debugging mode
• /prod-debug bootstrap — (re)build schema.md and containers.md from source files

---

On /prod-debug

Step 1: Find project root

Determine the project root — use the current working directory, or if inside a git repo, use git rev-parse --show-toplevel.

Step 2: Check for data directory

Check whether .claude/prod-debug/config.json exists at the project root.

• If missing: tell the user that prod-debug is not set up for this project yet, and suggest running /prod-debug bootstrap after creating .claude/prod-debug/config.json.
• If present: continue to Step 3.

Step 3: Load context files

Read all three data files using the Read tool:

1. {project_root}/.claude/prod-debug/schema.md
2. {project_root}/.claude/prod-debug/containers.md
3. {project_root}/.claude/prod-debug/prod-env.md

If any file is missing, note it and proceed with what's available.

Step 4: Check schema staleness

Run:

~/.trimkit/bin/trimkit-prod-debug-staleness {project_root}

It compares the newest migration matching migrations.glob against the prod-debug:last-migration marker in schema.md. It prints nothing (exit 0) when schema.md is current, and a one-line warning (exit 1) when it is stale or has no marker, e.g.:

[prod-debug] schema.md is stale (068_foo.sql vs 085_bar.sql) — run /prod-debug bootstrap.

If it prints a warning, include it verbatim at the top of the Step 5 announcement. If it exits 2 (or any other code), report its stderr verbatim instead: config.json or schema.md is unreadable, and the auto-sync hook is also disabled until that's fixed.

The check reads the local checkout the glob points at. Migrations merged by others don't show up until that checkout is pulled. Don't bootstrap automatically; offer to. If the script is not installed, do the same comparison by hand: newest matching migration filename vs the marker.