Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/jj-claude-plugin:spr-amendThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /spr-amend Modify an existing jj change and update its associated GitHub PR. ## Instructions **First:** Check if you're in a jj workspace (`.jj/repo` is a file, not a directory). If so, `cd` to the main colocated repo before proceeding. Use the `jj-spr-amend-update` skill to guide the amend-update cycle. 1. Ask the user which change to modify (or infer from context) 2. `jj edit <change-id>` to make it the working copy 3. Make the requested code changes 4. **MANDATORY:** `jj new <change-id>` to reposition `@` 5. Update the PR — always pass `-m` to avoid interactive prompt: `jj spr ...
Modify an existing jj change and update its associated GitHub PR.
First: Check if you're in a jj workspace (.jj/repo is a file, not a
directory). If so, cd to the main colocated repo before proceeding.
Use the jj-spr-amend-update skill to guide the amend-update cycle.
jj edit <change-id> to make it the working copyjj new <change-id> to reposition @-m to avoid interactive prompt:
jj spr diff -m "addressed feedback" -r <change-id>jj spr diff -m "updated mid-stack" -r <change-id>::<top>Never skip step 4. The user must be able to review with jj diff -r @-.
npx claudepluginhub edmondop/jj-claude-plugin --plugin jj-claude-plugin