create-issue
Create well-structured GitHub issues following best practices and conventions. Use when the user asks to create an issue or needs to track work.
Create well-structured GitHub issues following best practices and conventions. Use when the user asks to create an issue or needs to track work.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Bump the Blackpepper version, review full git diffs (including unrelated changes), craft a Conventional Commit message, and push the current branch. Use when the user asks to "verbump", "bump version", "increment version", "release", or explicitly requests version bump + commit + push for this repo.
Git 工作流与提交规范技能:标准化的 Git 操作流程和 Conventional Commit 规范。 Use when: 需要提交代码、创建分支、发起 PR、管理版本。 Triggers: "commit", "提交", "push", "推送", "branch", "分支", "PR", "pull request", "merge", "合并"
This skill should be used when the user asks to "review code with codex", "run codex review", "check code quality", "codex レビュー", mentions "レビューゲート", or before git commit/PR/merge/release. Performs iterative code review using read-only Codex CLI, with Claude Code making fixes until ok:true is achieved. Use after spec/PRD/requirements creation, major steps (>=5 files/new modules/public APIs/infra changes), and before git operations.
Write commit messages in the preferred generic style: `type: imperative summary` with backticks around code identifiers and no scope. Use when you are about to `git commit`, splitting work into multiple commits, or when the user asks you to commit code.
Scan project folder structure, validate organization, clone GitHub repository, and generate an inventory of available materials. First step of writer workflow. Use when starting a new manuscript project.
Manage GitHub labels - create, edit, delete, apply labels, and organize with color coding using gh CLI
Create properly formatted references to paths (files or folders) in a git repository. Use when writing docs that need to link to any path in the repo.
Examines git diffs between commits or branches with intelligent analysis. Provides unified diff format with comprehensive summaries including file statistics, rename detection, and merge commit handling. Outputs formatted diffs to /claudedocs for documentation and review purposes.
ローカルGitブランチを分析し、安全にクリーンアップします。マージ状態、古さ、リモート追跡状況によってブランチを分類し、削除すべきブランチを特定します。ユーザーが「ブランチを整理」「古いブランチを削除」と依頼した時にアクティベートします。
Use when user says 'gh project create', 'GitHub Project 作成', 'プロジェクト作成', 'create project', or discusses creating a new GitHub Project. Ensures projects have proper short description and README.
Use the gitbug mcp and learn about how code should look
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Advanced usage of conventional commits with breaking changes, issue references, and multi-file commits.
Draft a Conventional Commits message from either a short summary of changes or by inspecting the local git diff. Use when the user wants a commit message formatted as type(scope): subject, with optional body and footers for breaking changes or issue references.
Create and execute git commit plans from YAML files - use when organizing changes into logical commits or when user wants help structuring their git history
Use conventional commits aligned with Ralph workflow