deep-analyse
Skill315 starsChanged 10 months agoApache-2.0View on GitHub
Thorough code analysis without polluting main context
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- commit-helperSkill
- design-syncSkill
- docs-drift-reviewSkill
- doc-syncSkill
- sanity-checkSkill
- theme-auditSkill
- worktree-managerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Trace all code paths: Follow execution from entry points through to completion
- Distinctive: line 14
Identify side effects: Document state changes, I/O operations, and mutations
≈ “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.
Files
Deep Analysis
Perform thorough analysis of the specified code area: $ARGUMENTS
Analysis Steps
- Trace all code paths: Follow execution from entry points through to completion
- Map dependencies: Identify all imports, interfaces, and external dependencies
- Identify side effects: Document state changes, I/O operations, and mutations
- List callers and callees: Build a call graph for the target code
- Check test coverage: Identify which paths have test coverage and which lack it
Deliverables
Provide a structured report with:
- Architecture overview
- Key abstractions and their purposes
- Critical code paths
- Potential issues or improvement opportunities
- Test coverage assessment
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.