Menu
Ensure the current jj revision has a bookmark. Determines prefix from CLAUDE.md, analyzes changes to generate a topic name, and creates the bookmark.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | jj-set-bookmark |
| description | Ensure the current jj revision has a bookmark. Determines prefix from CLAUDE.md, analyzes changes to generate a topic name, and creates the bookmark. |
| allowed-tools | ["Agent"] |
Ensure the current revision has a bookmark.
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 setting a jj bookmark on the current revision. Inspect the LIVE state — do not trust any prior context.
1. Check if the project has a `CLAUDE.md` file at the repository root.
- Look for a line matching `## JJ Bookmark Prefix: <prefix>` (e.g., `## JJ Bookmark Prefix: joshua/`)
- If found, extract the prefix (including trailing slash if present)
- If not found, use no prefix
2. Run `jj log -r @ -T 'bookmarks'` to check if current revision already has a bookmark.
- If a bookmark already exists, report it and stop.
3. Find the branch point: `jj log -r 'ancestors(@) & bookmarks() & ~remote_bookmarks()' -n 1`
4. Analyze ALL changes from branch point to current:
- `jj diff -r '<branch-point>::@'`
- `jj log -r '<branch-point>::@' --no-graph -T 'description'`
5. Create a bookmark name: `<prefix><topic>` where topic is a short kebab-case description of the overall changes.
6. Set the bookmark: `jj bookmark set <name>`
7. Report what bookmark was set.
Always use `jj` commands, never `git`.
After the subagent returns, report the result to the user.