git-pre-commit
ユーザーが「コミットして」「コミット作って」「コミット前に確認したい」と言ったときに使う。gitの参照系サブコマンドを使って確認し、コミットするスキル。
Discover Blockchain skills, compare source repositories and read the instructions for each workflow.
ユーザーが「コミットして」「コミット作って」「コミット前に確認したい」と言ったときに使う。gitの参照系サブコマンドを使って確認し、コミットするスキル。
Creates SpecKit specifications (spec.md, plan.md) in feature/release/hotfix worktrees. Detailed implementation guidance. Use when: In worktree, need specifications, implementation planning Triggers: write spe...
Integrates git branches into default to keep it up to date. To be used when merging current branch into main or master branch
Maintain linked history entries in history.md. Use after any state change to record what changed and why.
Generate commit messages following project conventions for staged changes. Use when the user asks to commit changes or run /commit.
Pull request conventions and workflow for MuebleriaIris. Trigger: When creating PRs, reviewing code, or managing Git workflow.
GitHub Pull Request作成スキル - 変更内容の自動サマリー、PR説明文生成、GitHub PRの作成を行います。git diffでの変更分析、コミットメッセージ取得、変更ファイル分類を行い、高品質なPR説明文を自動生成します。qa-check...
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.
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.