commit-messages
MANDATORY when writing commit messages. Structures commits with type prefix, what+why body, and architectural file tree.
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
MANDATORY when writing commit messages. Structures commits with type prefix, what+why body, and architectural file tree.
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
Use when exploring a codebase to understand structure, find files, check dependencies, or see recent changes. Provides verified commands for effective exploration.
Generate environment setup guide documentation from codebase analysis. Detects package managers, required tools, environment variables, and startup commands. Triggers: setup guide, environment setup, developmen...
Command workflow orchestration patterns for /code, /fix, /audit, and other implementation commands. Use when implementing features with /code, /fix, /audit commands, or when user mentions workflow, ワークフロー...
CLI tools guide for git, gh, npm, and other development tools. Triggers: git, gh, npm, CLI, コマンドライン, バージョン管理, ブランチ, コミット.
Generate environment setup guide documentation from codebase analysis. Detects package managers, required tools, environment variables, and startup commands. Use when creating setup guides, documenting environm...
CLI tools guide for git, gh, npm, and other development tools. Use when executing git commands, managing branches, or when user mentions CLI, コマンドライン, バージョン管理, ブランチ, コミット.
Use when addressing PR review comments from Copilot, Claude, or human reviewers. Critically assesses each comment, recommends action (implement/push-back/discuss), and executes appropriately.
Read-only access to external repositories for cross-repo context. Use when you need to reference code, patterns, or documentation from other local repositories.
Manage git worktrees for parallel Claude Code development sessions
Handle squashing multiple commits and rebasing feature branches safely. Use when consolidating commits into a single commit, or rebasing feature branches onto updated development branches. Falls back from jj wh...
Jujutsu (jj) version control, load skill when hook output shows vcs=jj-colocated or vcs=jj in the system-reminder.
GitLab Flow workflow for implementing issues. Use when the user asks to work on a GitLab issue, fix an issue, implement an issue, or mentions an issue number to implement.
GitHub and Git workflow helpers; triggers on 'create pr', 'pr checks', 'retrigger tests', 'bump version', 'push'.
CodeRabbit CLIを活用したコードレビューエージェント。コミット前チェック・ファイルレビュー・セキュリティフォーカス・自動修正を担当。ファイル依存関係を認識した深い分析、AI幻覚検出。Judgeを補完。
End the current session. Converts transcript to markdown, writes summary, syncs files, commits, and pushes to GitHub and Blot.
Clean up git worktrees whose associated feature PRs have been merged. Only removes worktrees where the PR is confirmed merged - never removes active development worktrees.
Scan codebase to identify opportunities to replace custom implementations with well-maintained open source libraries. Creates worktree, implements changes, and submits PR for review. Multi-phase workflow with p...
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
Use when design is complete and you need detailed implementation tasks - creates tracked MCP issues with exact file paths, complete code examples, and verification steps. Optional reference plan file for archit...
Orchestrate spec-to-PR workflow with session tracking, worktree isolation, and audit trail
Initialize complete governance framework in a project - creates constitution, roadmap, directory READMEs, and issue/spec templates with guided setup process
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...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.