code-quality-metrics-standards
Skill15 starsChanged 5 months agoCC0-1.0View on GitHub
Analyzes code complexity and adherence to quality standards, flagging overly complex functions and metric outliers. Use when auditing maintainability, cyclomatic complexity, or coding-standard compliance.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 14
If no target path is given above, review the entire codebase.
- Distinctive: line 20
Look for complex functions/methods.
- Distinctive: line 67
Prefer minimal, drop-in fix snippets over prose.
- Distinctive: line 69
Do not invent files or functions that aren’t present.
- Distinctive: line 71
Write this into a markdown file and place it in the audits/ folder.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Target: $ARGUMENTS
If no target path is given above, review the entire codebase.
Analyze code complexity across the codebase:
Look for complex functions/methods.
Also look at functions/methods and calculate/evaluate:
- CYCLOMATIC COMPLEXITY
- Functions with complexity > 10
- Nested if/else depth
- Switch statement complexity
- Recommend refactoring for high complexity
- COGNITIVE COMPLEXITY
- How hard is the code to understand?
- Nested loops and conditions
- Recursive calls
- Mixed levels of abstraction
- LINES OF CODE METRICS
- Functions over 50 lines
- Files over 300 lines
- Classes over 500 lines
- Identify candidates for splitting
- COUPLING METRICS
- Afferent coupling (dependencies on this module)
- Efferent coupling (dependencies of this module)
- Instability index
- Identify tightly coupled modules
- COHESION ANALYSIS
- Are related functions grouped?
- Single responsibility adherence
- Module focus clarity
Provide specific refactoring recommendations for complex areas.
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.
In this repository21 other files it gives its agents.
- api-and-infrastructureSkill
- authentication-flow-reviewSkill
- authorization-implementationSkill
- business-logic-vulnerabilitiesSkill
- code-duplication-detectionSkill
- comprehensive-security-reportSkill
- database-securitySkill
- design-pattern-implementationSkill
- error-handling-resilienceSkill
- exception-flow-analysisSkill
- file-handling-business-logicSkill
- initial-security-analysisSkill
- initial-software-design-analysisSkill
- input-validationSkill
- logging-monitoringSkill
- readability-and-namingSkill
- resilience-fault-toleranceSkill
- secrets-management-auditSkill
- session-cookie-securitySkill
- solid-principlesSkill
- testing-implementationSkill
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.