branch-creator
Issue 番号に基づいて feature ブランチを自動作成する。「ブランチ作成」「ブランチを作って」「新しいブランチ」「feature ブランチ」「Issue からブランチ」「作業ブランチを作成」「ブランチ切って」などで起動。feature/[issue番号] 形式でブランチを作成。
Issue 番号に基づいて feature ブランチを自動作成する。「ブランチ作成」「ブランチを作って」「新しいブランチ」「feature ブランチ」「Issue からブランチ」「作業ブランチを作成」「ブランチ切って」などで起動。feature/[issue番号] 形式でブランチを作成。
GitHub issue lifecycle management with worktree isolation
Expert GitHub CLI and PR handling. Use when working with pull requests, GitHub issues, reviews, CI checks, or any gh command operations.
Make a GitHub issue self-contained for a single feature/fix so any coding agent can execute it without back-and-forth. Focus on scope, file touchpoints, acceptance criteria, and validation.
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
コミットメッセージの命名規則を設定する。「コミットメッセージ設定」「コミット規則」「コミット形式を設定」「コミットメッセージルール」「commit message 設定」「コミットの書き方を設定」「コミットフォーマット」などで起動。プロジェクト固有のコミットメッセージルールを管理。
Open source contribution best practices. Creating quality pull requests, writing good issues, following project conventions, and collaborating effectively with maintainers.
他者の PR をレビューして GitHub にコメントを投稿する(レビュアー向け)。「PR レビュー」「PR をレビュー」「コードレビュー」「レビューして」「セキュリティレビュー」「パフォーマンスレビュー」などで起動。
Use when planning Rails features or breaking down work into PRs - enforces 2-5 file PRs, bug fix separation, and one-sentence scope test
사용자의 간단한 기능 설명을 바탕으로 GitHub 기능 티켓을 자동으로 생성합니다. 프론트엔드, 백엔드, 공통, 인프라 섹션별로 세부 태스크를 체크박스 형태로 작성하고, gh issue create 명령으로 Mockly-Company/.github 레포에 직접 생성합니다. 버그 리포트나 문의가 아닌, 새로운 기능 개발 티켓 생성 시에만 사용합니다.
Create a new feature branch following Git Flow strategy. Use when starting new feature development, creating a branch for an issue, or when user says "create branch", "new feature", "start working on issue".
Anthropic Best Practices 기반 TDD 워크플로우. Red-Green-Refactor 강제.
Generate conventional commit messages by analyzing repository changes following conventionalcommits.org specification
Clone a Git repository as bare repo and set it up for git worktrees workflow. Use when the user says "clone as bare repo", "setup git worktrees", "worktree clone", or asks to clone a repo for worktree usage.
Posts or updates the PR summary comment. Detects context (GitHub sticky comment, GitHub new comment, or local file) and routes output accordingly. Use after all findings are classified and inline comments are posted.