Takeover
Take over existing work. Use when the user asks to take over a PR, branch, or agent thread, or requests a takeover.
Install
npx skills add t3dotgg/tstack --skill takeovergit clone --depth 1 https://github.com/t3dotgg/tstack.git /tmp/tstack
mkdir -p ~/.claude/skills
cp -r /tmp/tstack/skills/takeover ~/.claude/skills/takeoverPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
Details
- Skill name
takeover- Repository
- t3dotgg/tstack
- Path
skills/takeover/SKILL.md- License
- MIT
- Repo updated
- 11 November 2026
FAQ
What does the Takeover skill do?
Take over existing work. Use when the user asks to take over a PR, branch, or agent thread, or requests a takeover.
How do I install the Takeover skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add t3dotgg/tstack --skill takeover. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Takeover popular?
It lives in t3dotgg/tstack, which has 4,154 GitHub stars and 323 forks.
Related skills
Babysit PR
4.2kt3dotgg/tstack
Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.
File PR
4.2kt3dotgg/tstack
File a concise pull request. Use when the user asks to file, open, or create a PR.
Full Stop
4.2kt3dotgg/tstack
Trigger this if the user says 'full stop', even as a closing "Full stop." that reads like emphasis.
Code Review
3.3krpamis/comet
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Publish Project to Github
7.7kMengTo/Skills
Package a finished local project into an intentional GitHub repository, create a strong README and visual preview, push it safely, configure a public GitHub Pages URL when the project is compatible, and verify the deployed result. Use when a user asks to upload, publish, open-source, share, or turn a local HTML/CSS/JavaScript experiment or small web project into a documented GitHub repository with a live demo.
Fable Review
4.3kdavidondrej/skills
Launch an independent Fable code review and return it verbatim. Use for /fable-review, or when the user or another agent asks for a Fable review.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.