commit-message
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Discover databases git workflows skills, compare source repositories and read the instructions for each workflow.
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
ローカルリポジトリの変更を分析し、コードレビューを実施する
Creates logical git commits from working tree changes. Use when finishing work, saving progress, or organizing changes into commits.
Detect whether the current project uses jj (Jujutsu) or git for version control. Run this BEFORE any VCS command to use the correct tool.
Maintains requirement IDs and traceability mapping. Invoke when adding/changing features or tests to keep PRD coverage accurate.
Create atomic git commits following project conventions with chunk-based staging
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
Archive multiple completed changes at once. Use when archiving several parallel changes.
Git 提交信息规范和最佳实践。用于编写清晰、规范的提交信息,遵循 Conventional Commits 标准。
Comprehensive code review using all available skills. Use before committing or when you want a thorough analysis of changes. Triggers on review code, check changes, full review, pre-commit review.
Generate concise, conventional commit messages from git staged changes. Use when (1) user asks for a commit message, (2) user wants to summarize staged changes, (3) user says "commit", "staged changes", or "git...
Examine commits since the last tag, categorize changes by type (breaking/feature/fix), and recommend the appropriate semantic version bump
Create a new git worktree with iTerm integration. Use when asked to create, add, or start a new worktree.
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"
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.