Menú
Create a new child revision and move all changes made since the last push into it, leaving the pushed revision clean.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | jj-new-since-push |
| description | Create a new child revision and move all changes made since the last push into it, leaving the pushed revision clean. |
| allowed-tools | ["Agent"] |
Create a new child revision and move all changes made since the last push into it, leaving the pushed revision clean.
CRITICAL: Conversation context may contain stale jj state (old diffs, descriptions, logs). You MUST dispatch a subagent to inspect the live jj state directly. Do NOT rely on any jj output already in the conversation.
Spawn a subagent with the following prompt:
You are moving post-push jj changes to a new child revision. Inspect the LIVE state — do not trust any prior context.
1. Run `jj log -r @ -T 'bookmarks'` to get bookmarks on current revision.
- If output is empty, report error: "No bookmark found on current revision. Use `jj bookmark create <name>` to create one." and stop.
- Extract the bookmark name (use the first one if multiple exist).
2. Run `jj diff -r '<bookmark-name>@origin..@' --stat` to check for changes since push.
- If output is empty (no changes since push):
- Run `jj new` to create a new child revision
- Report: "No changes since last push. Created new child revision."
- Stop here.
3. Move post-push changes to new revision:
- Get the current revision ID: `jj log -r @ -T 'commit_id' --no-graph`
- Get the old bookmark commit ID: `jj log -r <bookmark-name> -T 'commit_id' --no-graph`
- Move the bookmark back to origin: `jj bookmark set <bookmark-name> -r <bookmark-name>@origin --allow-backwards`
- Create new child revision: `jj new <bookmark-name>`
- Restore changes from the saved current revision ID: `jj restore --from <current-rev-id>`
- Abandon the old bookmark commit: `jj abandon <old-bookmark-commit-id>`
- Report: "Moved post-push changes to new child revision. Parent revision now matches remote."
Always use `jj` commands, never `git`.
The bookmark name should be the local bookmark (without `@origin`).
The `--allow-backwards` flag is required when moving a bookmark to an ancestor.
After the subagent returns, report the result to the user.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Comprehensive code review using 5 independent specialized reviewer agents in parallel (security, performance, correctness, code quality, spec compliance). Confidence scoring (0-100), per-repo pre-flight/post-fix commands via docs/agents/review.md. Use when user wants code review, says "review this", or invokes /review.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub, GitLab, Linear, or local markdown), triage label vocabulary, domain doc layout, review configuration, and hook wiring. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, `zoom-out`, or `review` — or if those skills appear to be missing context about the issue tracker, triage labels, domain docs, or review config.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.