菜单
Use for generic commit-related intent in `.jj/` repositories. Must be paired with `jujutsu` in the same turn; never use it as a standalone skill. Explicit Git-only `.jj` commit intent routes to `git-commits`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run end-to-end GitHub issue triage using the local triage scripts and parallel subagent scoring. Use when asked to create, refresh, or rerun issue triage markdown with complexity, difficulty, benefit, scope, and execution-lane recommendations (`agent-implementation`, `agent-assist-human`, `human-only`).
Find and resume a past Claude Code, Codex, or Cursor Agent conversation by searching session history files by keyword. Use this skill whenever the user wants to find a previous conversation, can't remember which directory or agent they were using, wants to look up work from a past session, needs to resume a session they can't locate with /resume, codex resume, or agent --resume, or says something like "I know we discussed X somewhere" or "where was that session about Y". Infers search scope, agent, and keywords from the user's description and presents matching sessions with summaries before asking which to resume. Always use this skill rather than manually searching ~/.claude/, ~/.codex/, or ~/.cursor/ yourself.
Use for commit-level Git workflows in non-`.jj/` repositories: stage one logical change, write or revise commit messages, amend, create fixup commits, split bundled edits, curate history with rebase or autosquash, and verify bisectability. In repositories containing `.jj/`, use this skill only for explicit Git-only commit intent; generic commit intent routes to `jujutsu` plus `jj-commits`. Trigger on requests such as "commit this", "check it in", "ship it", "stage and commit", "amend", "fixup", "clean up history", "reword/split commits", or "draft/rewrite the commit message". Also use for indirect commit-message creation when drafting plans that specify commits (including `superpowers:writing-plans` outputs), and when writing commit message text in design docs, PR notes, or other artifacts.
Guidelines for designing and implementing command-line interfaces. Use when creating a new CLI tool, adding subcommands or flags to an existing one, implementing help text, designing error messages, or structuring CLI output. Also use when reviewing CLI code for usability, when the user asks about CLI best practices, or when generating argument parsers, config handling, or shell completions. Applies to any language.
Apply Christopher Larson's preferred Bash and POSIX shell script style when creating or substantially editing user-facing shell scripts. Use when writing or modifying shell utilities under `scripts/` or `script/` (including extensionless shebang executables, pre-commit entry scripts, and CI helpers), `.sh` files, shell snippets intended for the user to keep, or any Bash or POSIX sh program that will become part of the maintained codebase. Do not use for temporary test scripts, disposable intermediate artifacts, or scripts written solely for AI-agent execution.
Use when working with version control in a repository that contains `.jj/`, or when the user explicitly mentions Jujutsu or `jj`. When the VCS context is ambiguous, check for `.jj/` in the working tree before defaulting to plain Git. Do not use this skill as the primary route for non-`.jj/` generic Git tasks.
| name | jj-commits |
| description | Use for generic commit-related intent in `.jj/` repositories. Must be paired with `jujutsu` in the same turn; never use it as a standalone skill. Explicit Git-only `.jj` commit intent routes to `git-commits`. |
Commit-policy defaults for jj repositories.
Use this skill only for commit-quality and commit-series hygiene in .jj
contexts. This skill does not define jj command mechanics.
Invoke jujutsu in the same turn; it owns jj mechanics and sequencing that this skill does not cover. This skill applies to generic commit intent in .jj contexts only; explicit Git-only intent uses git-commits instead.
This skill owns jj commit policy:
This skill explicitly excludes:
Use jujutsu for jj mechanics, operation sequencing, and command-level flow.
Follow the seven rules of commit messages:
Subjects describe the change, not the workflow event that produced it. Replace "Fix tests", "Address review", or "Continue work on X" with descriptions of the actual code change.
For commit message bodies longer than two sentences, invoke the clean-prose skill before finalizing. Subject lines and one-line bodies don't need it.
Treat the branch as a coherent patch series:
During development, temporary commits are acceptable. Before review, curate the series into clear logical steps and remove workflow-noise commits.
Before pushing for review, run jj log -r '<base>..@' (where <base> is the merge target, e.g., main) and read the series. Each subject describes a code change; bodies explain why; no temporary or workflow-noise commits remain; the order tells a coherent story. If any check fails, curate before pushing.
