菜单
Use when the user wants to write a git commit message — including 'write a commit message', 'commit this', or when they paste a diff / staged changes and ask what to commit it as. Follows Conventional Commits. Do NOT use for PR descriptions (use pr-description skill).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks to review code, perform a code review, analyze changes for issues, or review a PR/diff. Runs linting, typechecks, and tests to provide comprehensive feedback. Do NOT use for simple questions about code (use the explore agent instead).
Use when the user wants to write, improve, or fill in a GitHub pull request description. Triggers: 'write a PR description', 'draft a PR', 'fill in the PR template', 'summarize this diff', or when the user pastes a diff / commits and asks for a PR body. Do NOT use for commit messages (use commit-message skill) or release notes.
Use when the user wants to write a git commit message — including 'write a commit message', 'commit this', or when they paste a diff / staged changes and ask what to commit it as. Follows Conventional Commits. Do NOT use for PR descriptions (use pr-description skill).
Use when the user wants to write, improve, or fill in a GitHub pull request description. Triggers: 'write a PR description', 'draft a PR', 'fill in the PR template', 'summarize this diff', or when the user pastes a diff / commits and asks for a PR body. Do NOT use for commit messages (use commit-message skill) or release notes.
| name | commit-message |
| description | Use when the user wants to write a git commit message — including 'write a commit message', 'commit this', or when they paste a diff / staged changes and ask what to commit it as. Follows Conventional Commits. Do NOT use for PR descriptions (use pr-description skill). |
Write commit messages that follow Conventional Commits.
<type>(<scope>): <subject>
<body>
<footer>
feat, fix, refactor, test, chore, docsauth, api, parserBREAKING CHANGE: ... or Closes #123! after type/scope for breaking changes: feat(api)!: drop v1 endpoints.git status output if not provided.feat, bugfix -> fix, etc.).BREAKING CHANGE: footer if applicable.feat(auth): add OAuth login via GitHub
Users can now sign in with their GitHub account. Uses the standard
OAuth2 flow; tokens are stored in httpOnly cookies.
Closes #142
fix(parser): handle empty input without crashing
refactor(api)!: rename /users endpoint to /accounts
BREAKING CHANGE: /users is removed. Update clients to use /accounts.