Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Clean up after a feature branch or experiment is complete. This skill deletes the git worktree and branch ONLY AFTER the associated PR has been merged. It also closes any related GitHub issues. Use this after y...
Automatically draft commit messages by analyzing git status and staged changes
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
git worktree を利用した分離作業環境を自動構築します。デフォルトブランチから最新コードを取得し、.git-worktrees/ ディレクトリに新規worktreeを作成、.env・npm依存関係を自動セットアップします。ブランチ名の '/' は自...
Generate commit message and automatically commit staged changes. ONLY use when user explicitly invokes /git-cm slash command. Do NOT trigger on general git questions.
This skill should be used when reviewing GitHub Pull Requests to provide comprehensive code quality, security, and architecture analysis with optional JIRA ticket integration.
Guide for basic Git operations
Generate conventional commit messages following official Conventional Commits specifications https://www.conventionalcommits.org/en/v1.0.0/#summary. Use when asked to generate commit messages, to analyse change...
Manage git worktrees with the wt CLI - create, switch, list, and delete worktrees with automatic dependency installation and graphite tracking
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
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...
커밋 메시지 생성 스킬. 다음 상황에서 자동 호출: - "커밋", "commit", "커밋 메시지", "커밋해줘", "커밋 부탁" - "변경사항 커밋", "staged 커밋", "git commit"
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
PR作成Skill。仕様レビュー用または実装レビュー用のPRを作成。/spec や spec-workflow から呼び出される。
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.
Switch to a worktree in iTerm. Use when asked to switch, open, or go to a worktree.
Create or update SKILL.md files for this repo. Use when authoring skills in .claude/skills/.
Generate Conventional Commits messages and run git add/git commit from current repo changes. Use when the user says "git commit" or asks to auto-stage changes and craft a commit message from the diff.
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...
Inspire team repository inventory and standards. Use when understanding the codebase structure or repository conventions.
Create a pull request following project PR guidelines and template. Use this when asked to draft or create a PR.
Resume work on existing feature clone
Tools for fetching GitHub PR/issue/commit comments cleanly via gh CLI. Use when needing to retrieve comment data from GitHub with structured JSON output.
Provides commands and patterns for Data Version Control (DVC). Use when the user asks about versioning large files, creating pipelines, or reproducing experiments.
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.