Sync git repository with upstream. Use at the start of a session, when asked to sync, get up to date, check git status, or when working on a stale branch. Checks branch status, uncommitted changes, PR state, and upstream drift, then takes appropriate actions.
Manage Git worktrees for working on multiple branches simultaneously without cloning the repository
変更をGitコミットしてTDDサイクルを完了する。REVIEWの次フェーズ。「コミットして」「commit」で起動。
Find and answer unanswered GitHub discussions. Activate when user wants to contribute to open source discussions, help answer GitHub questions, or find discussions to answer. Delegates all work to subagents.
Use only when the user explicitly asks for a git branch name. Output one strong recommendation in a consistent pattern, with minimal, high-signal rationale.
Create feature spec files from project docs, commit and push to main, and create matching feature branches from main.
Gitを使用した開発ワークフローのルールです。ブランチの変更、Worktreeの作成、Pull Requestの作成時に必ず確認し遵守してください。
Craft concise commit messages with technical precision
Link a project to a GitHub repository. Requires authentication
Use when asked to publish or sync a feature branch to pre in this repo, or to resolve complex git conflicts that occur in that release flow.
Create a new feature module in the dotfiles following the 'Package by Feature' directory structure. Handles creation of darwin.nix and home.nix, and updates parent imports.
Merge conflict resolution conventions. Use when resolving git merge conflicts, especially in dependency files and lock files.
Generates clear commit messages following project conventions
Create GitHub pull request with atomic Beads issue closure. MUST BE USED for opening PRs. Asks if work is complete - if YES, closes Beads issue BEFORE creating PR (JSONL merges atomically with code). If NO, creates draft PR with issue still open. Automatically links Beads tracking and includes Feature-Key. Use when user wants to open a PR, submit work for review, merge into master, or prepare for deployment, or when user mentions "ready for review", "create PR", "open PR", "merge conflicts", "CI checks needed", "branch ahead of master", PR creation, opening pull requests, deployment preparation, or submitting for team review.
Complete individual tasks with test-first development, quality gates, and proper commits. Use when working on bugs, features, or tasks that result in a single commit.
Use BEFORE significant TODO modifications (adding subtrees, marking complete, reorganizing, collapsing). Ensures policy compliance through extractive questions. Run proactively when planning TODO changes.
Use after PR merge to complete iteration cycle. Supports Ralph Loop for iterative PM refinement. Syncs Linear status, commits with standards, creates Postmortems for significant incidents, and crystallizes high-frequency rules into CLAUDE.md.
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", or "pr for these changes". Does NOT merge - stops when CI passes and provides the PR link.
Review a Gitlab Merge Request. Use when the user says "review" or "code review" or asks to review pull requests, merge requests, or analyze branch changes before merging
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
