Menü
Interactive chunk-by-chunk code review using jj.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | review-walk |
| description | Interactive chunk-by-chunk code review using jj. |
Based on Ben Gesoff's review workflow.
jj duplicate <target>
jj edit <duplicated-change-id>
jj new --no-edit --insert-before @ -m 'review: <description>'
Note both IDs:
@-) — accumulates approved code@) — unreviewed diffjj diff --stat
jj diff
jj log -r '@' -T 'description' --no-graph
Group into logical chunks by: semantic concern, dependency order, file proximity, risk level. Present the plan, let the user adjust.
For each chunk:
jj diff -- <paths>)On approval:
# VISUAL=true prevents editor popup when squashing empties @
VISUAL=true jj squash --from @ --to @- -- <file1> <file2>
# Hunk-level:
jj squash -i
Show progress:
jj diff --stat # remaining
jj show @- --stat # approved so far
jj interdiff --from <original-change-id> --to @-
Produce summary with: findings, changes made, approved chunks, unreviewed items, verdict.
Teardown:
# No changes made — abandon both
jj abandon --from @- --to @
# Changes made — abandon original, keep review commit
# Never squash review commit into original — both add the same files from scratch,
# which creates a conflict.
jj abandon <original-change-id>
jj abandon @
jj edit main # pause
jj edit <duplicate-id> # resume
/skill:review-walk # current change
/skill:review-walk main # bookmark
/skill:review-walk kowqznzo # change ID
/skill:review-walk abc::def # range
Browser automation via agent-browser. Use when the user wants to browse, interact with, or inspect web pages.
Review agent-facing knowledge (rules, AGENTS.md, CONVENTIONS.md, README.md, domain docs) for staleness and accuracy. Use when the user asks to audit, clean, or prune knowledge. Also use when they're confused by a rule/doc that seems wrong — treat that as the starting point for a broader audit.
Reflect on session, update rules, commit with jj.
Adversarial design interview.
Ingest sources into the wiki.
Wiki health checks.