Loading...
Loading...
Found 169 Skills
Use Git worktrees for isolated work environments. Creates separate working directories for parallel development on different branches.
Create alpha-forge git worktrees with auto branch naming. TRIGGERS - create worktree, new worktree, alpha-forge worktree.
Fork terminal sessions to spawn parallel AI agents or CLI commands in new terminal windows. Supports git worktrees for isolated parallel development.
Planが承認/完了した直後に自律的に呼び出す必要があるスキルです。 Trigger: plan approved, plan completed, taskを開始します
Guide for using git worktrees to parallelize development with coding agents. Use this skill when the user requests to work in a new worktree or wants to work on a separate feature in isolation (e.g., "Work in a new worktree", "Create a worktree for feature X").
Execution-type Core-Lite Git worktree skill (only supports help/init/do/check/merge). Default execution without parameters is init --new + do exec; high-risk commands are only permitted via the CLI latch --yes --i-am-maintainer; lock conflicts default to SAFE_NEXT=init --new. Execution commands only read route-bash/route-powershell.
Manage AI coding agents on a visual Kanban board. Run parallel agents through a To Do→In Progress→Review→Done flow with automatic git worktree isolation and GitHub PR creation.
Perform common Git operations safely with sandbox-aware failure handling. Use whenever the user wants to inspect or modify git state, especially for cherry-pick, merge, rebase, commit, branch, stash, or worktree workflows. Always use this skill when the user mentions a Git failure, conflict, cherry-pick, merge issue, worktree, branch checkout problem, lock file, permission denied, operation not permitted, or any case where a sandboxed agent might confuse an environment restriction with a real code conflict. Be proactive: if the task smells like Git state or Git write behavior, use this skill even if the user did not explicitly ask for a 'Git' workflow.
[Hyper] Commit and push in one action, including from linked Git worktrees. Use when the user asks to commit and push together, save and push changes, or run `/git-maker`; it performs safe commit grouping first, then automatically pushes without a second confirmation.
This skill should be used when the user asks to "create a worktree", "new worktree", "worktree for feature", "git worktree", or needs to work on a feature branch in isolation. Handles Rails credential symlinking automatically.
Guide for running multiple parallel Claude Code sessions using cw (Claude Worktree Manager). Use when the user wants to parallelize work across multiple Claude instances, manage git worktrees for concurrent AI coding tasks, or merge results back together. Triggers on tasks involving parallel Claude sessions, worktree management, or splitting work across multiple agents.
Guide for working in parallel with other agents. Use when another agent is already working in the same directory, or when you need to work on multiple features simultaneously. Covers git worktrees as the recommended approach.