takeover — Claude Code skill for handoffs
A skill for Claude Code that picks up unfinished work on a PR, branch, or agent thread. It activates when asked to take over.
MIT 1,200 installs ★ 4,278 updated 2026-11-11
npx skills add t3dotgg/tstack --skill takeover -a claude-codeWhat takeover does
The skill reads the source PR, branch, or thread, including review feedback and later user corrections, then carries the original goal forward. It checks the handoff against the current code and accounts for uncommitted changes.
For a replacement PR, it moves the original commits to a new branch and adds fixes separately; an in-place continuation follows an explicit request. The skill preserves contributor and co-author credit, independently checks the original failure and realistic workflows, and reports what remains unverified. It only changes or closes the original PR when authorized.
When finishing the task includes a PR, it uses file-pr to create or update it, then babysit-pr to follow up; replies go through leaving-pr-comments. modernize updates the continuation against its intended base and current architecture.
What it helps with
- hand off unfinished work on a PR
- carry review feedback and later corrections into a branch
- continue work with uncommitted changes in view
- preserve contributor credit in a replacement PR
- verify the original failure and report unchecked cases
Example prompts for the agent
- Take over this PR and finish the original goal.
- Pick up this branch, including the review feedback and my latest corrections.
- Take over this agent thread and work out what remains to finish.
How to install takeover
1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill takeover -a claude-code2Manually: put the files in place
~/.claude/skills/takeover/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/takeover/
1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill takeover -a codex2Manually: put the files in place
.agents/skills/takeover/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill takeover -a cursor2Manually: put the files in place
.cursor/skills/takeover/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install t3dotgg/tstack skills/takeover2Manually: put the files in place
.github/skills/takeover/SKILL.md1Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill takeover -a gemini-cli2Platform CLI
gemini skills install https://github.com/t3dotgg/tstack --path skills/takeoverManually: put the files in place
.devin/skills/takeover/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add t3dotgg/tstack --skill takeover -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about takeover
How do I install takeover in Claude Code?
Run npx skills add t3dotgg/tstack --skill takeover -a claude-code. The skill file is at ~/.claude/skills/takeover/SKILL.md.
What does takeover do?
It helps resume work on a PR, branch, or agent thread, compare the handoff with the current code, and complete the original goal while preserving contributor credit.
How does takeover preserve contributor credit?
It keeps Git authorship and existing co-author trailers, and credits contributors in the PR description. For squash merges, it also preserves human authorship in the merge commit using verified identities.
Source text
SKILL.md · MIT
--- name: takeover description: Take over existing work. Use when the user asks to take over a PR, branch, or agent thread, or requests a takeover. --- # Takeover Take responsibility for finishing the original goal while preserving the original contributors' credit. Do not defend an implementation just because another agent already built it. Read the source PR, branch, or thread, including review findings and the user's later corrections. Resolve the handoff to the actual code and current head, and account for uncommitted work. Treat the handoff as context, not proof. For a replacement PR, import the original commits onto a new branch and add your fixes separately. Honor an explicitly requested in-place or stacked continuation instead. Do not overwrite unrelated work or change the original PR without authorization. Preserve Git authorship and existing co-author trailers. Credit the original contributors in the PR description and link the original PR when there is one. If the work will be squashed, preserve human author/co-author credit in the merge commit too, using verified identities rather than guessed emails. Model attribution is not a substitute for contributor credit. Use `modernize` to update the continuation against its intended base and current architecture. Rework what is necessary to finish the same goal, not unrelated features. Simplify the implementation without dropping intended behavior or surfaces. Recheck the source PR too: it may have improved while you were working. Independently verify the original failure and realistic workflows, following repository guidance and permissions. Green mocked tests do not prove the user experience works. State what remains unverified. When the requested finish includes a PR, use `file-pr` to file or update it, then `babysit-pr` rather than stopping at creation. Use `leaving-pr-comments` for replies. Merge or close the original PR only when authorized. Report what you inherited, what you changed, how you verified it, how credit was preserved, and any remaining decision.
© t3dotgg · MIT · t3dotgg/tstack