Git運用ガイドライン、ブランチ戦略、コミットメッセージ（Conventional Commits）、プルリクエスト作成、個人開発とチーム開発の使い分けを定義する。Gitコミット作成時、ブランチ作成時、PR作成時、またはユーザーがコミットメッセージ、ブランチ戦略、バージョン管理、Conventional Commits、Semantic Versioningに言及した際に使用する。

RevTechStudio

devops

open

git-workflows

accept-pr

Land one PR end-to-end (changelog + thanks, lint, merge, back to main).

doubleflannel

devops

open

git-workflows

safe-commit

git commit を行う際に自動発動。禁止ディレクトリ（ai/, .serena/）のコミット防止と、論理的なコミット分割を支援する。

biosugar0

devops

open

git-workflows

prime

Prime the context with project information

dave-007

devops

open

git-workflows

This skill should be used when the user asks to "set up notes worktree", "create documentation branch", "separate docs from code", "keep markdown in separate branch", "symlink documentation", "move docs to separate branch", or discusses keeping markdown files in a separate git branch while maintaining access via symlinks in the main project.

hbbayrak

devops

open

git-workflows

using-git-worktrees

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

eyadsibai

devops

open

git-workflows

write-skills

Create or update SKILL.md files for this repo. Use when authoring skills in .claude/skills/.

JoernStoehler

devops

open

git-workflows

complete

Finalize a completed ticket: write 5-final.md, update 4-progress.md, commit. WHEN TO USE: - All required tests pass (via /pmc:ticket-status) - Ready to mark ticket as COMPLETE or BLOCKED - User says "complete ticket", "finalize", "wrap up ticket" PRODUCES: - 5-final.md with Status: COMPLETE or BLOCKED - Updated 4-progress.md frontmatter - Git commit: "T0000N: complete"

jayprimer

devops

open

git-workflows

pr-create

Use this when creating a pull request

TravisBumgarner

devops

open

git-workflows

task-breakdown

Break work into trackable tasks and maintain TODO.md. Use when starting features, bug fixes, or complex tasks. Always update TODO.md after completing work.

antoncoding

devops

open

git-workflows

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Jetaofgak

devops

open

git-workflows

copilot-cli

Use when you need to run or troubleshoot GitHub Copilot CLI (npx @github/copilot), including sessions, permissions (--allow-tool/--deny-tool), MCP management (/mcp), or Copilot CLI agents.

QuinnRuth

devops

open

git-workflows

commit

Create commit messages following conventional commit conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with issue references.

mpuig

devops

open

git-workflows

commit

Commit with user prompts from this conversation. Use when user mentions committing, wants to commit changes, asks to save their work to git, or says "commit this".

stared

devops

open

git-workflows

repo-release-guardrails

Protect against wrong-repo edits and enforce production parity assumptions.

paulyd-oi

devops

open

git-workflows

smith-gh-cli

GitHub CLI gotchas and best practices. Use when executing gh commands. Covers token efficiency, pagination limits, and common pitfalls.

tianjianjiang

devops

open

git-workflows

gh-pr-review

GitHub PR review operations (inline comments, pending reviews, thread resolution)

rcdailey

devops

open

git-workflows

doc-sync

Keep project documentation (CLAUDE.md, .env.example) in sync with actual configuration changes. Use after major configuration changes, environment setup modifications, or when user requests "update documentation" or "sync docs with current setup".

mim1012

devops

open

git-workflows

openspec-propose

Use when adding features, changing behavior, or modifying architecture. Creates change proposal with specs and tasks. ALWAYS ask for approval before proceeding to implementation. Do NOT use for bug fixes or trivial changes.