Initial software design analysis
Skill JeremyMorgan/code-review-skills/skills/initial-software-design-analysis
Produces a first-pass architecture and design review covering structure, maintainability, and scalability. Use when onboarding to or assessing the design of a codebase.From its SKILL.md
npx -y skills add JeremyMorgan/code-review-skills --skill initial-software-design-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as CC0-1.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, as published. Nobody here has run it
Target: $ARGUMENTS
If no target path is given above, review the entire codebase.
Initial Software Design Analysis:
Analyze the project architecture and identify:
Evaluate:
- Is there clear separation of concerns?
- Which architectural pattern is used (MVC, Layered, Microservices)?
- Are there any God objects or modules doing too much?
- Is the dependency flow clean (no circular dependencies)?
- Rate the modularity (1-10) with justification
Create an architecture diagram showing:
- Layer dependencies
- Data flow
- External service integrations
- Potential bottlenecks
Identify anti-patterns:
- Spaghetti code
- Copy-paste programming
- God classes/modules
- Tight coupling
- Missing abstractions
Provide:
A structured finding report
A scale of 1/10 on how important each finding is
Remediation: precise code-level fix or config change (snippets welcome) if possible
Constraints & style:
Be concrete and cite exact code locations and identifiers.
Prefer minimal, drop-in fix snippets over prose.
Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.
Write this into a markdown file and place it in the audits/ folder.