write-commit-message
Use when creating git commits to ensure consistent, clear commit messages following conventional commits format.
Use when creating git commits to ensure consistent, clear commit messages following conventional commits format.
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
Generate conventional commit messages from staged changes. Runs autonomously using Haiku model. Use after completing TDD cycles, after refactoring sessions, or when ready to commit.
Systematic approach to GitHub release preparation following 2025 best practices for Rust workspace projects
Use when you need a Conventional Commits message from staged git changes or a pasted diff - guides type/scope selection and subject/body/footer formatting for a compliant commit message
Use when creating pull requests to write clear, structured PR descriptions that help reviewers understand changes.
Keep pull requests and issues healthy using gh CLI (list, view, comment, close).
Git worktreeを使った並列開発を支援する。複数のClaude Codeインスタンスで同時に異なるブランチの作業を行う際に使用する。"worktree"、"並列開発"、"別ブランチで作業"などのキーワードで発動。
Reimplement the current Git branch on a fresh branch off `main` with a clean, narrative-quality commit history.
Use when starting feature work that needs isolation, or when completing work and deciding how to integrate - covers full worktree lifecycle from setup through merge/PR/discard
Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits.
Initialize complete governance framework in a project - creates constitution, roadmap, directory READMEs, and issue/spec templates with guided setup process
Generate clear conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or after completing TDD cycles.
A comprehensive guide for configuring and using Terrateam, an open-source GitOps CI/CD platform for Terraform and OpenTofu. Covers configuration file structure, access control, workflows, OIDC authentication, drift detection, and best practices for managing infrastructure through pull requests.
When you need to understand the directory structure, open-core model, or where to add new code.
End the current session. Converts transcript to markdown, writes summary, syncs files, commits, and pushes to GitHub and Blot.
Use when creating research or plan documents to gather git commit, branch, repository info.
"Work with git worktrees and workspaces for concurrent development. Use when: (1) Creating new workspaces with \`git worktree add\`, (2) Listing existing worktrees with \`git worktree list\`, (3) Removing worktrees with \`git worktree remove\`, (4) Pruning stale worktree metadata with \`git worktree prune\`, (5) Managing multiple checked-out branches simultaneously, (6) Migrating uncommitted work between workspaces, or (7) Any git workspace/worktree operation. Requires Git 2.5+ for worktree support."
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.
This skill should be used when reviewing code or preparing code for review. It provides guidelines for what to look for in reviews, how to write constructive feedback, and standards for review comments.
Use when starting new feature work to create isolated git worktrees with smart directory selection and safety verification. Keeps main branch clean while developing.
CLI tools guide for git, gh, npm, and other development tools. Triggers: git, gh, npm, CLI, コマンドライン, バージョン管理, ブランチ, コミット.
Orchestrate replying to multiple GitHub PR review comments in parallel. Use when the user wants to reply to multiple PR review comments or resolve all unresolved comments on a PR.