メニュー
Ensure the current jj revision has a proper conventional commit description. Analyzes the diff, generates a message, and offers the user a choice if one already exists.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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-desc |
| description | Ensure the current jj revision has a proper conventional commit description. Analyzes the diff, generates a message, and offers the user a choice if one already exists. |
| allowed-tools | ["Agent","AskUserQuestion"] |
Ensure the current revision has a proper commit description.
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. Pass through the project's CLAUDE.md commit guidelines if you have them.
You are setting a jj commit description. Inspect the LIVE state — do not trust any prior context.
1. Run `jj log -r @ --no-graph -T 'description'` to get the current description.
2. Run `jj diff -r @` to see the actual changes in this revision.
3. Generate a conventional commit message for ALL changes in this revision:
- Format: `type(scope): description` (lowercase, no period)
- Types: feat, fix, refactor, docs, test, chore, etc.
- Additional lines are OK if they add value (blank line after first line)
- Description is for CURRENT COMMIT ONLY
4. If an intentional description already exists:
- Consider BOTH the code changes AND the existing description
- The existing description may contain important context not obvious from code
- Preserve valuable context from the original while ensuring accuracy
- If your suggestion differs meaningfully, report BOTH the current and suggested descriptions back
- Do NOT update the description yourself — just report both options
5. If no description exists (or it's a placeholder like "checkpoint", "wip", "latest updates"):
- Set it with `jj describe -m "<message>"`
- Report what you set
Always use `jj` commands, never `git`.
NEVER add "Generated with Claude Code" or "Co-Authored-By: Claude" lines.
After the subagent returns:
jj describe -m "<chosen message>" yourself