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. Presents exactly 4 options: merge locally, create PR, keep as-is, or discard. Do NOT use when tests are failing or work is incomplete - fix issues first before finishing the branch.
Create conventional commits from staged/unstaged changes. Use when user asks to commit, create commits, commit changes, commit all, make commits, separate commits, commit everything, stage and commit, commit these changes, save and push, commit this work, or requests push after committing. Handles single or multiple commits, staging, message generation from diffs, and push operations.
Manages branches/merges. Use for switching/creating/deleting branches, merging. Triggers - feature branches, PRs.
Git workflow enforcement and best practices. Use when: - Writing commit messages or reviewing commits - Creating branches or choosing merge strategies - Setting up CI/CD pipelines with git operations - Resolving merge conflicts or rebasing - Configuring repository settings or git hooks - Optimizing large repository performance Keywords: git, commit, branch, merge, rebase, PR, pull request, trunk-based, conventional commits, atomic commits, git hooks, CODEOWNERS
Manage git-tracked directories correctly - never create .gitkeep files in directories that will immediately contain tracked files
Use for change discipline, validation expectations, and safety checks when making repo changes.
Use when completing tasks, implementing major features, or before merging
Execute GitHub CLI commands using the correct Homebrew path. Use when interacting with GitHub PRs, issues, repos, or any gh command.
PR 코드 리뷰 코멘트를 체계적으로 해결하는 skill. 사용자가 (1) PR 리뷰 코멘트 해결을 요청하거나, (2) 코드 리뷰 피드백을 반영하려고 하거나, (3) "리뷰 코멘트", "PR 코멘트", "코드 리뷰" 관련 수정을 언급할 때 사용. 1 코멘트 → 1 작업 → 1 테스트 → 1 커밋의 원칙으로 진행하며 진행 상황을 YAML로 추적.
Guide for Git operations including commits, branches, rebasing, conflict resolution, and following Git best practices and conventional commits
Commits changes, pushes to remote, and creates a draft PR. Use when: user wants to commit and create PR in one flow.
bmorphism's GitHub stars (2155 repos) and created repos - a curated index
Create changesets for package changes in pull requests. Use whenever you modify code in any package (packages/*). Required before committing changes to packages. Handles versioning with patch for bug fixes, minor for features, and major only when explicitly requested.
Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not performative agreement or blind implementation.
Commit staged changes only using Conventional Commit parameters (validates inputs).
Validate code, commit, push, and create PR if needed
Use to spawn isolated worker processes for autonomous issue work. Creates git worktrees, constructs worker prompts, and handles worker lifecycle.
Generate new Nix configuration modules following the repository's standard pattern. Creates module boilerplate in system/, darwin/, or home/ directories with proper options structure, imports parent default.nix automatically, and follows best practices for module organization.
