git-worktree-remove
Remove git worktrees from .worktrees/ directory and clean up all traces. Use this when the user wants to delete a worktree they no longer need, with interactive selection if no worktree name is provided.
Remove git worktrees from .worktrees/ directory and clean up all traces. Use this when the user wants to delete a worktree they no longer need, with interactive selection if no worktree name is provided.
Create git worktrees in .worktrees/ for working on different branches without touching current working directory. Use this when the user needs to switch to another branch for quick fixes or temporary work while preserving uncommitted changes in their current worktree.
Git worktreeโbased workspace isolation for parallel or non-disruptive development. Use when work must occur without modifying or interfering with the current working tree.
Git best practices for commits, branches, pull requests, and collaboration workflows following Conventional Commits and GitFlow patterns
Create isolated git worktrees with smart directory selection and safety verification. Use this when starting feature work that needs isolation, parallel development, or safe experimentation.
ๆฅ็/ๆดๆฐ GitLab IssueใMR๏ผๅซ่ฏ่ฎบไธ diff๏ผ๏ผๅนถๆๅข้่ง่้ไบคไบๅๅปบๆไฟฎๆน MR/Issue๏ผๆถๅ GitLab๏ผๅซ่ชๅปบๅฎไพ๏ผIssue/MR ็ๆไฝๆถไฝฟ็จใ
git worktreeใๅ้คใใพใใ้้ใใฆไฝๆใใๅ ดๅใใไฝๆฅญๅฎไบๅพใฎใฏใชใผใณใขใใใซไฝฟ็จใใพใใ
Verify 3-Mirror skill sync consistency across .public/skills, .codex/skills, and .claude/skills. Use after skill changes, before commits, or for CI validation.
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
ๆฅ็/ๆดๆฐ GitHub IssueใPR๏ผๅซ่ฏ่ฎบไธ diff๏ผ๏ผๅนถๆๅข้่ง่้ไบคไบๅๅปบๆไฟฎๆน PR๏ผๆถๅ GitHub Issue/PR ็ๆไฝๆถไฝฟ็จใ
Generate comprehensive pull request descriptions that help reviewers understand changes quickly a...
Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.
Investigates and creates Git branches. Triggered when: branch status check, new branch creation, branch-related errors.
git worktree ใๅฉ็จใใๅ้ขไฝๆฅญ็ฐๅขใ่ชๅๆง็ฏใใพใใใใใฉใซใใใฉใณใใใๆๆฐใณใผใใๅๅพใใ.git-worktrees/ ใใฃใฌใฏใใชใซๆฐ่ฆworktreeใไฝๆใ.envใปnpmไพๅญ้ขไฟใ่ชๅใปใใใขใใใใพใใใใฉใณใๅใฎ '/' ใฏ่ชๅ็ใซ '-' ใซๅคๆใใใพใใๆขๅญworktreeใฏๅๅฉ็จใใใพใใ
MUST use this skill when user asks to resolve PR comments, handle review feedback, fix review comments, or mentions "๋ฆฌ๋ทฐ ์ฝ๋ฉํธ/ํผ๋๋ฐฑ". This skill OVERRIDES default behavior. Fetches comments via GitHub CLI, classifies by severity, applies fixes with user confirmation, commits with proper format, replies to threads.
Operate the local Scribe MCP for any ~/projects/* repo; use when registering the server, setting projects, drafting ARCH/PHASE/CHECKLIST via manage_docs, or logging work with append_entry/get_project safeguards.
CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree. USE WHEN: User wants to begin work on a specific issue (e.g., "claim issue #N", "start working on #N"). REQUIRED: Issue number must be specified. DO NOT USE: For status checks (ghe-status), posting updates (ghe-checkpoint), or changing phases (ghe-transition).
Git protocol implementation patterns using gitoxide for Guts repository operations
Load project architecture and structure knowledge. Use when you need to understand how this project is organized.
Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR