research-codebase
Skill1 starsChanged 50 days agoAGPL-3.0View on GitHub
Conduct comprehensive codebase research with parallel sub-agents. Use when user asks to "research codebase", "analyze code", "investigate", "understand the code", "how does X work", or wants to document how existing code functions.
9 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- lithammer/aitheir own version, first seen Oct 17, 2026
- charly-vibes/incitacionestheir own version, first seen Oct 14, 2026
- sipandey/create-agent-roomtheir own version, first seen Sep 26, 2026
- atomicinnovation/acceleratoredited, first seen Sep 22, 2026
- jurgendn/agent-skillstheir own version, first seen Sep 17, 2026
- liorhai5/ai-skillstheir own version, first seen Sep 7, 2026
Used with
Projects with it also use describe-pr.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
parcadeiSkilldescribe-pr
Generate comprehensive PR descriptions following repository templates
Also in 4 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- atomicinnovation/accelerator★ 3413% same
- corticalstack/flow★ 122% same
Wrote their own version · 7
- joshuaalpuerto/mcp-agent★ 18same name
- jurgendn/agent-skills★ 10same name
- fabianmagrini/skills★ 1same name
- charly-vibes/incitaciones★ 0same name
- liorhai5/ai-skills★ 0same name
- lithammer/ai★ 0same name
- sipandey/create-agent-room★ 0same 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commitSkill
- create-planSkill
- fix-bugSkill
- frontend-designSkill
- implement-planSkill
- init-trackerSkill
- iterate-planSkill
- linearSkill
- validate-planSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 19 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 9 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.
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.