414 skills · sorted by relevance
GitHub Issue を作成する。タスクは Issue 本文内でチェックボックスに分割。「Issue 作成」「Issue を作って」「タスクを Issue に」「Issue 追加」「チケット作成」「Issue を切る」「タスクを分割して Issue」などで起動。「ブランチも」「worktree も」と伝えれば作成後にブランチ/worktree も用意する。
The English summary is being prepared. Showing the original description.
Manage complex Git histories with guidance for reorganizing commits, copying selected changes between branches, and finding bug-introducing commits. It also covers working on multiple branches at once and recovering lost commits through Git's reference history.
Create separate Git working directories for issue fixes, pull request reviews, and feature development. Optional tmux terminal sessions help manage parallel tasks, return to ongoing work, and clean up completed sessions.
Prepare a Python SDK release candidate in a separate working directory, check version metadata and public API compatibility, and produce one local commit with a review report for the release handoff.
Delegate research, coding, and testing from Claude Code to opencode workers. Run independent tasks in parallel with separate Git working directories, combine findings, track token use, and compare solo execution with coordinated workers.
Delegate checks for AGENTS.md rule violations to a dedicated agent. It scans the codebase, fixes high-impact issues in a separate working copy, runs full validation, and creates a pull request, tracking progress across runs through memory.
Open Plannotator’s browser-based code review interface from Kiro and address the returned feedback. Review the current directory, another working directory, or a pull request URL, and optionally choose a comparison base to focus the changes shown.
Finish completed development work by verifying tests and the target branch, then choosing a local merge, a pull request, or leaving things unchanged. Cleanup follows the chosen action and respects who manages the working directory.
Turn a feature request into an approved demo narration, then use that script to guide implementation in an isolated workspace. Verify each demo frame against the real app and open a pull request with the supporting results.
Follow Squad's Git workflow from issue branches through pull requests and cleanup. It covers development from dev, isolated directories for parallel issues, coordinated changes across repositories, and promotion to preview, insiders, and stable releases.
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
Use Git worktrees to isolate parallel coding tasks. Use when setting up a task checkout, working in a shared repo, or managing existing worktrees.
The English summary is being prepared. Showing the original description.
Git worktree management for safe, isolated feature development. Creates, manages, and cleans up worktrees with branch naming and dependency setup.
The English summary is being prepared. Showing the original description.
AI DevKit · Worktree setup and resume guidance for isolated feature work. Use when starting, resuming, switching, or verifying a feature branch/worktree for lifecycle, debugging, implementation, review, or multi-agent workflows.
The English summary is being prepared. Showing the original description.
Isolate repository edits in a Git worktree before starting a feature, fix, or documentation change. Preserve a worktree already assigned to the same task. Read-only reviews and investigations do not need a new worktree.
The English summary is being prepared. Showing the original description.
Triage, repair, and close MCP attribution issues from the local report API with evidence-driven decisions and isolated Worktrunk worktrees. Use this skill when Codex needs to process `tool` attribution issues and skills-related attribution issues, inspect related runs, decide whether the issue is actionable in `mcp/src` or `config/source/skills`, update attribution fields as `owner=codex`, and then complete the fix loop through GitHub issue tracking, worktree-based code changes, PR submission, and follow-up iteration when the problem is repairable.
The English summary is being prepared. Showing the original description.
Mandatory rules for agents in git worktree isolation.
The English summary is being prepared. Showing the original description.
Set up isolated git worktrees. Use when starting isolated work, or when ce-work/ce-code-review offers a worktree option; detect existing isolation first.
The English summary is being prepared. Showing the original description.
Executes a groomed milestone with parallel kage-bunshin sessions in isolated worktrees. Use when a milestone has been groomed and /groom-milestone has produced a dispatch plan. Reads the dispatch plan, creates an integration branch, spawns one kage-bunshin (independent claude -p process) per wave item in its own worktree — each session is a full orchestrator with the Agent tool. Sequentially merges worktree branches, relays wave discoveries to subsequent waves, then lands the integration branch to main. Takes a milestone number as argument.
The English summary is being prepared. Showing the original description.
Report which local git worktrees under tmp/ are safe to close, need a human look, or are explicitly protected. Use when the user says /fleet-audit, asks what worktrees can be cleaned up, or wants a status check across all Ralph-loop/spike worktrees before running closeout on any of them.
The English summary is being prepared. Showing the original description.
Git worktree management for working on multiple branches in parallel. Create, list, remove, and synchronize worktrees. Protects against direct pushes to master.
The English summary is being prepared. Showing the original description.
Coordinate safely with a peer interactive session sharing the same git worktree — check first whether a separate worktree removes the problem, then declare path and branch scope before the first edit, survive a contended index lock, and review the whole branch before opening a PR. Activate when starting work in a repository that may already be occupied, when a git command fails with `index.lock: File exists`, when `guard:snapshot` refuses because a snapshot already exists, or when a commit turns out to contain a file this session never edited. When one session leads and the other supports, divide the labour by shape and re-derive every reported number against a named revision before citing it. Distinct from subagent concurrency: a peer session cannot be bracketed, because no baseline exists from before its edits.
The English summary is being prepared. Showing the original description.
Meta-agent supervisor that manages a fleet of Claude Code agents running in tmux windows. Auto-discovers spare worktrees, spawns agents, monitors state, kicks idle agents, approves safe confirmations, and recycles worktrees when done. TRIGGER when user asks to supervise agents, run parallel tasks, manage worktrees, check agent status, or orchestrate parallel work.
The English summary is being prepared. Showing the original description.
Audits git repository hygiene: worktree state, stale branches, uncommitted changes, orphaned worktrees, and hook configuration. Finds the rot before it causes a crisis.
The English summary is being prepared. Showing the original description.