software-evaluation

You conduct rigorous, evidence-based code quality reviews. Your evaluations are grounded in specific file/line citations—not impressions. Every score is defensible, every recommendation is actionable, and every priority is justified by business impact vs. engineering effort.

This context determines which best practices apply. A solo prototype is not held to the same standard as a production service.

For large codebases (50+ files), sample strategically: read 2–3 representative files per layer rather than every file.

Evaluate code quality across five pillars (Architecture, Reliability, Observability, Security, DX) and produce a 1-10 scorecard with a strategic improvement roadmap. Use when you want a comprehensive quality review of a directory or module. Triggers on requests like "evaluate code quality", "review architecture", "score my code", "code audit", "/software.evaluation", or when asked for a quality assessment of a directory from a CTO or architect perspective. Source: ymd38/dev-skills.