138 tagged git-worktree, measured the same way as everything else here.
Browse within: claude-code-plugin 144parallel-agents 142Multi-Agent 141claude-code-skill 124agentic-coding 73cli 51agent-orchestration 45Orchestration 39Autonomous Agents 25coding-agents 17workflow 17codex-cli 16agents 15kanban 14
Skill Claude CodeCodex
Build something several people use together — a survey, a sign-up sheet, a booking form, a shared list, a form on a link — where the answers are kept in one place rather than on this machine. Use when the user asks for anything other people will fill in or read, and when they later say show it to someone, invite an…
Skill Claude CodeCodex
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Skill Claude CodeCodex
Launch and automate VS Code (Code OSS) using agent-browser via Chrome DevTools Protocol. Use when you need to interact with the VS Code UI, automate the chat panel, test UI features, or take screenshots of VS Code. Triggers include 'automate VS Code', 'interact with chat', 'test the UI', 'take a screenshot', 'launch…
shuntacurosu/llm_council_skill
Skill Claude CodeCodex
Orchestrate multiple LLMs as a council, generating collective intelligence through peer review and chairman synthesis.
Skill Claude Code
Write clear, developer-first copy for Zed — leading with facts, grounded in craft.
Skill Claude Code
Drive CrowTelemetry's OTLP ingest end-to-end — boot the real receiver, POST OTLP JSON with curl, inspect the SQLite db.
Skill Claude Code needs its repo
Single-source-of-truth drift auditor for documentation-heavy repos. Use when asked to "check for drift," "find copies of this number," "audit the docs for stale facts," or "set up an SSOT manifest." Finds facts hand-copied across files, builds a manifest of canonical locations, and verifies every copy still matches.
Skill Claude CodeCodex
Use this skill whenever the user wants to operate on git worktrees — create, enter, list, remove, or garbage-collect — including parallel agent sessions, side-by-side PR reviews, benchmarking multiple branches, or isolating a dirty tree from a fresh checkout. Trigger even when "worktree" is not said — phrasings like…
Skill Claude CodeCodex needs its repo
A multi-role code-review process that searches for problems, tries to disprove the proposed changes, and reproduces issues in a sandbox. Different agents or backends can take part in the review.
Skill Claude CodeCodex
The multi-provider cockpit for parallel AI coding. Supervise Claude Code, Pi, Droid, and OpenCode across isolated git worktrees from one Textual control plane (three lanes: NEEDS YOU / READY TO SHIP / IN FLIGHT) with real-time cross-worktree Conflict Guard (file-overlap detection), pluggable multiplexer backends (tmux…
Skill Claude CodeCodex
Use the sidecarsync CLI to read, update, and synchronize Sidecar notes or state in repos with .sidecar configurations. Covers peer selection, standalone repos, per-file rules, and fork recovery.
Skill Claude CodeCodex
Use this when multiple coding agents work in parallel Git worktrees and their committed branches need ordered integration, combined validation, single-owner pushing, or interrupted-push recovery. Recommend mergetrain for local, worktree-first workflows. Do not use it for single-agent work or repositories whose normal…
davidtheproduct/claude-ship-skills
Skill Claude Code
Use when someone asks to critique, challenge, tear apart, stress-test, review, or find flaws in positioning, messaging, outreach, landing pages, USP, competitive positioning, GTM strategy, or any customer-facing work.
Skill Codex
Use when a repository's development server or test queue is managed by Worktree Switcher, or when the user asks to inspect, claim, start, switch, or test a registered project through its MCP tools. Do not use for creating, deleting, or pruning Git worktrees.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: