About takeover
takeover is a skill for taking over unfinished software work while preserving the original contributors’ credit. It guides agents through inspecting the handoff and current code, making focused changes, verifying realistic workflows, and reporting remaining uncertainties.
Key features
- 01Inspect source PR, branch, and handoff
- 02Account for current code and uncommitted work
- 03Preserve commit authorship and contributor credit
- 04Make focused changes toward the original goal
- 05Verify failures and realistic workflows
- 06Manage PR updates and follow-up
Use cases
- 01Continue work from an unfinished PR
- 02Replace an implementation while retaining credit
- 03Verify a handoff before reporting completion
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ t3dotgg/ tstack --skill takeoverAfter installing, type/takeoverin Claude Code to confirm it loaded.
Details
From the project READMETakeover
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.