generating-commit-messages
MANDATORY skill for ALL commits. Must be used EVERY TIME before creating any git commit. No exceptions.
MANDATORY skill for ALL commits. Must be used EVERY TIME before creating any git commit. No exceptions.
実装完了後に PR を作成し関連 Issue をクローズする。「PR 作成」「PR を作って」「プルリク作成」「pull request」「PR 出して」「プルリクエスト」「PR を出したい」などで起動。変更内容を分析し適切な PR を生成。
Watch a GitHub UAT PR for maintainer feedback or approval by polling comments until approved/passed.
Manages Git Worktree parallel development. Required when starting new work. Creates worktrees with wt- prefix for parallel development. User confirmation required before creation.
コミットメッセージ作成スキル。Conventional Commits形式の日本語メッセージを作成。Use when: コミット作成、変更内容のコミット、git commitを依頼された時。
Create conventional commit messages and plan commits. Use when a user asks to commit changes, write commit messages, or organize commits. Enforce repo-specific git/commit rules from AGENTS.md and split multiple logical changes into separate, digestible commits.
Deep analysis of GitHub repositories to understand their core architecture, design philosophy, technical decisions, and implementation patterns. This skill should be used when users provide a GitHub URL and request comprehensive understanding of the repository's structure, purpose, key abstractions, or technical approach.
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 or blind implementation
Conventional commits, PR practices, branching strategies
Automacao de criacao de branches baseado em tipo de trabalho. Integra com SpecKit para criar branches automaticamente ao iniciar features. Use quando: iniciar novo trabalho, criar feature, corrigir bug.
Creates comprehensive PR descriptions by systematically reviewing ALL changes - features, bug fixes, tests, docs, and infrastructure. Use when user asks to "update the PR", "prepare PR for review", "write PR description", or "document branch changes". Requires gh CLI.
You are an implementer of GitHub issues. You are an Agent who has been assigned an issue to work on.
Review RFCs for the ToolHive ecosystem. Use when the user wants to review, critique, or provide feedback on an RFC for toolhive, toolhive-studio, toolhive-registry, toolhive-registry-server, toolhive-cloud-ui, or dockyard projects.
Generate a conventional commit message from staged changes. Analyzes changes to determine affected packages and appropriate commit type, then outputs a properly formatted commit message.
Git変更の論理的分割、Conventional Commitsメッセージ生成、プロジェクト規約検出。大きな変更を意味のある最小単位に分割してコミットする際に使用。
Use when spec verified and ready for implementation to orchestrate development using isolated workspace and quality gates - sets up worktree, executes tasks via subagent-driven or sequential approach, verifies completion, and finishes development branch
Generate conventional commit messages by analyzing repository changes following conventionalcommits.org specification