git-worktrees
Create, list, and remove git worktrees for parallel agent work. Use when you need isolated workdirs, new worktree branches, or safe cleanup workflows.
Create, list, and remove git worktrees for parallel agent work. Use when you need isolated workdirs, new worktree branches, or safe cleanup workflows.
Filesystem operations within workspace boundaries
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with sisyphus_task(category='quick', skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
Validates that no secrets or sensitive data are being committed to the repository
Initialize project with stack-specific configuration. Use when user wants to set up repository for a specific technology stack (Node.js, Python, Rust, Go).
Create isolated git worktree, open new iTerm2 window with Claude Code, and spawn a task agent there for parallel work. Use when the user says "parallelize" followed by a task description, or asks to work on something in parallel.
Third step in building instruction context for codebase
Core repo preferences: simplicity-first, DRY, and avoid compatibility shims unless explicitly requested.
Help address GitHub PR review comments. Use when the user mentions PR reviews, code review feedback, reviewer comments, or needs to resolve review threads.
Finalize and archive a progress file for a GitHub PR: locate the related docs/progress file (prefer PR body Progress link), set Status to DONE, move it to docs/progress/archived/, update docs/progress/README.md, merge the PR with gh, patch the PR body Progress link to point to the base branch so it survives branch deletion, and (when present) patch the planning PR body to include an Implementation PR link. Use when a feature PR is ready to be closed and its progress tracking should be marked DONE.
Initialize ÆtherLight in a new repository. Sets up folder structure, Git workflow, configuration files, and development standards.
Instructions for writing Go code following idiomatic Go practices and community standards
요구사항 명세를 기반으로 프로젝트 아키텍처와 GitHub Actions CI 파이프라인을 설계합니다. "프로젝트 시작", "프로젝트 초기화", "CI 설정", "아키텍처 설계" 등의 요청 시 활성화됩니다.
Create git commit for all uncommitted changes in the repository
Use when creating or merging pull requests - provides branch naming, PR title format, and description requirements for consistent PR workflows
Fetch unresolved PR review comments and feedback on the current branch. Use when you need to address outstanding PR review items or see what feedback needs to be resolved. Optionally filter by a specific reviewer.
Ensures all file operations occur in the correct worktree directory to prevent accidental changes to the wrong codebase. Use when implementing, reviewing, testing, or documenting code in worktree-based development workflows.