codebase-investigation
Skill2 starsChanged 9 days agoNo licenceView on GitHub
Read-only investigation that explains code and its history. Use for "how does X work", code walkthroughs before changing something, placement and ownership questions ("where should this live", "which package owns this", "is this the right layer"); for "why does X work this way", "why did we pick Y", design rationale, regressions, postmortems, and data-backed thresholds (cited, confidence-tiered archaeology across git, PRs, tickets, docs, chat, observability, error tracking, and analytics connectors); for researching a technical question against primary sources into one cited file; for "teach me this", "help me really understand X", or learning a topic over several sessions in a teaching workspace; and for "wait, what?" moments when an explanation did not land and needs a re-pitch in plain Simplified Technical English using the project glossary. Produces explanations and recommendations, not code changes.
In this repository28 other files it gives its agents.
- adversarial-reviewSkill
- ask-ericSkill
- bug-diagnosisSkill
- business-discoverySkill
- decision-mappingSkill
- delivery-planningSkill
- delivery-proofSkill
- engineering-principlesSkill
- feature-implementationSkill
- idea-assessmentSkill
- issue-triageSkill
- multi-agent-deliverySkill
- performance-investigationSkill
- pr-deliverySkill
- process-improvementSkill
- project-environmentSkill
- project-maintenanceSkill
- project-principlesSkill
- project-releaseSkill
- refactoringSkill
- session-continuitySkill
- standards-spec-reviewSkill
- system-verificationSkill
- technical-designSkill
- technical-writingSkill
- test-driven-developmentSkill
- verification-harnessSkill
- workflow-prototypeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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.