walking-a-pr-logic-diff-in-request-orderlisted
Install: claude install-skill sblattj/agent-chandlery
## More triggers
pr-logic-trail (old name)
# walking-a-pr-logic-diff-in-request-order
GitHub shows a PR file by file, alphabetically, tests mixed in. This shows only production code, in call order, with the impact of each change tagged.
## Do this
1. **Prep** (read-only; needs `gh` auth for the repo):
```bash
${SKILL_DIR:-~/.claude/skills/walking-a-pr-logic-diff-in-request-order}/scripts/trail.py prep <pr> --repo <owner/name> --out <out-dir>/pr-<n>-trail
```
Writes `logic.diff`, `hunks.md` (every logic hunk as `file [idx] +a -r header`, plus the excluded test files) and a `stops.json` skeleton. `--force` overwrites an edited `stops.json`.
2. **Read the logic diff** (`logic.diff`) in full. Before tagging anything shared, check the PR head for who else calls it (fetch `pull/<n>/head`, then grep or the `codebase-memory` graph). A change pitched as feature-only once turned out to hit production because the helper it touched was also called by the main build path.
3. **Fill `stops.json`**:
- `stops`: one per hop in the request path (contract, UI, service, downstream...). Number them only because they really are a sequence.
- `items`: `{file, hunks:[idx], impact, title, note, fold}`. Every hunk must be assigned exactly once.
- `impact` is one of:
- `prod`: changes behavior of live or already-shipped paths.
- `feature`: runs only in the new or changed feature path.
- `plumb`: imports, docs, pass-through wiring. Plumbing gets `fold: true`.