take-it

Ships GitHub issues in parallel via worktree sub-agents that open and merge PRs.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill take-it-sassy-dog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: take-it
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/take-it
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill take-it-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping multiple GitHub issues one at a time is slow and serial. This Skill takes a list of issue numbers and dispatches one isolated sub-agent per issue, each working in its own git worktree, so several fixes are implemented, reviewed, and merged concurrently without branch collisions. ## Core Features & Use Cases - Parallel worktree dispatch: Each issue gets its own sub-agent in an isolated git worktree, with guards against shared-state traps like git stash and editable installs. - Pre-flight and claiming: Skips closed, blocked, assigned, or stub issues; claims survivors with assignee and in-progress labels to prevent double-picks across sessions. - Review gate and coordinator loop: Runs a configurable review agent per changeset, then a coordinator polls PRs to auto-merge greens and surface failures. - Stacked PR support: Detects declared issue chains and ships them as ordered stacked PRs from a single agent when configured. - Use Case: Say "take #341, #432" and the Skill claims both issues, ships two PRs with Closes #N, and merges them once checks pass. ## Quick Start Ask the agent to take GitHub issues #341 and #432 and ship them as pull requests in parallel.

Frequently Asked Questions about take-it

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ship multiple GitHub issues in parallel?

Hand the agent a list of issue numbers, such as "take #341, #432". It dispatches one sub-agent per issue in its own git worktree, implements each fix, opens a PR with Closes #N, and a coordinator merges green PRs.

How many issues can be dispatched at once?

The Skill caps each dispatch at 5 sub-agents. Remaining issues are queued for the next round, and the resolved list is echoed before dispatching so you can confirm the batch.

Does take-it work without repo configuration?

No. If .claude/sassy-dog/take-it.md is missing, the Skill stops and tells you to run the setup-config skill first, because dispatching sub-agents without a stack summary or pre-flight commands produces low-quality PRs.

Can it handle dependent issues as stacked PRs?

Yes, when a stacked_prs block is configured and the issues declare a stack chain. One sub-agent builds the layers in order in a single worktree, opening each PR against the layer below; otherwise issues ship independently.

What happens when an issue is already assigned or blocked?

Pre-flight skips issues that are not open, carry a blocked label, already have an assignee, or are marked in progress. Claiming is idempotent and skips issues assigned to someone else, preventing double-picks across parallel sessions.

Why did a sub-agent's tests pass but test the wrong code?

Editable or global installs into a shared interpreter repoint imports for all parallel worktree agents, so a green run may test another agent's source. The Skill instructs agents to use a throwaway venv inside their own worktree instead.