reverse-engineer
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Systematically reverse-engineer an unfamiliar or inherited codebase — map its architecture, trace data flow, extract conventions, and flag risk areas — before making changes. Use when the user picks up a legacy project, inherits a module/repo with no docs or CLAUDE.md, or asks to understand/analyze an existing codebase before working in it.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- Firzus/agent-skillstheir own version, first seen Nov 1, 2026
- afonsoft/skillstheir own version, first seen Nov 1, 2026
- patrick-fu/awesome-skillstheir own version, first seen Nov 1, 2026
- loootai/reverse-engineertheir own version, first seen Nov 1, 2026
- umararshad4/honey-stacktheir own version, first seen Nov 1, 2026
- laaielichter/Reverseporttheir own version, first seen Oct 20, 2026
Used with
Projects with it also use debug-issue, orchestrate and 3 more.
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.
NVIDIASkilldebug-issue
Use when the user asks to debug, investigate, or fix a GitHub issue or supplies a repository bug report.
Also in 3 projects that use this
varun29ankuSSkillorchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
Also in 3 projects that use this
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 4 projects that use this
- NVIDIASkill
research
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 4 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- boshu2/agentops★ 453same name
- patrick-fu/awesome-skills★ 69same name
- laaielichter/Reverseport★ 18same name
- kevinbadi/open-edits★ 17same name
- afonsoft/skills★ 14same name
- rade-nugroho/Agentic-Enteprises-Skill★ 9same name
- xfstudio/skills★ 9same name
- daemon-blockint-tech/Agentic-Enteprises-Skill★ 8same name
- tstapler/dotfiles★ 8same name
- alvinhayy/Mobile-ReverseSkill★ 6same name
12 more not listed
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 repository3 other files it gives its agents.
- dev-teamSkill
- layer4-data-source-modelSkill
- stock-analysisSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 18 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.
Reviews can't be read right now.
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.