takeover
Skill3 starsChanged 5 months agoApache-2.0View on GitHub
Take over existing work. Use when the user asks to take over a PR, branch, or agent thread, or requests a takeover.
9 other projects use a version of this, 2 of them edited; 1 of 2 edited versions we compared changed its rules; 2 new projects in the last 4 weeks, against 0 the 4 before.
How people change it
1 of 2 edited versions changed its rules.
Of the 2 edited versions we compared: 1 keep every rule, 1 made changes of their own.
Rules people drop
- Use
modernizeto 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. …dropped by 1 of 1
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Surging: 2 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- adelrodriguez/skillstheir own version, first seen Nov 15, 2026
- every-app/open-seotheir own version, first seen Nov 8, 2026
- Belweave/hstacktheir own version, first seen Nov 8, 2026
- shubrt/skillsword for word, first seen Nov 1, 2026
- oubakiou/skillstheir own version, first seen Nov 1, 2026
- mneves75/skillsedited, first seen Nov 1, 2026
Other versions9 projects use a version of this.
Word for word · 2
- t3dotgg/tstack★ 3.8k100% same
- shubrt/skills★ 0100% same
Edited · 2
- Dhruv2mars/skills★ 386% same
- mneves75/skills★ 335% same
Wrote their own version · 5
- every-app/open-seo★ 28ksame name
- assisjp/specflow★ 17same name
- adelrodriguez/skills★ 1same name
- Belweave/hstack★ 1same name
- oubakiou/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- skills/supabase-postgres-best-practices/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- skills/supabase-postgres-best-practices/CLAUDE.mdCLAUDE.md
- ai-app-security-auditSkill
- ai-slide-templatesSkill
- babysit-prSkill
- backlog-ready-specSkill
- check-compiler-errorsSkill
- clawpackerSkill
- councilSkill
- deslopSkill
- devex-reviewSkill
- file-prSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- founder-office-hoursSkill
- full-sendSkill
- full-stopSkill
- get-cookiesSkill
- get-pr-commentsSkill
- gh-issue-priority-handoffSkill
- image2-with-codexSkill
- investigateSkill
- leaving-pr-commentsSkill
- local-ultra-reviewSkill
- modernizeSkill
- npm-release-pipelineSkill
- peer-reviewSkill
- plan-devex-reviewSkill
- planmode-ceoSkill
- planmode-engineerSkill
- qa-onlySkill
- review-and-shipSkill
- run-smoke-testsSkill
- security-best-practicesSkill
- site-design-auditSkill
- site-design-fixSkill
- slow-is-fastSkill
- sol-loopSkill
- supabase-postgres-best-practicesSkill
- vercel-react-best-practicesSkill
- xianyu-api-client-skillSkill
- xianyu-automation-skillSkill
- xianyu-product-manager-skillSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the source PR, branch, or thread, including review findings and the user's later corrections.
- Distinctive: line 23
If the work will be squashed, preserve human author/co-author credit in the merge commit too, using verified identities rather than guessed …
- Very specific: line 27
Use modernize to update the continuation against its intended base and current architecture.
- Very specific: line 37
When the requested finish includes a PR, use file-pr to file or update it, then babysit-pr rather than stopping at creation.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

