repo-analyze-strict

A strict repository audit requires reading a minimum sample of 20 source files to evaluate project structure, code quality, security, and CI/CD. It generates reproducible, evidence-backed grades by citing concrete findings and remediation guidance for every evaluation aspect.

A comprehensive repository audit evaluates project structure, documentation, architecture, code quality, testing, security, reliability, CI/CD, and governance. It enforces strict grading standards by requiring concrete evidence from source files for every grade improvement.

Run an exhaustive audit from the repository root to generate a reproducible, evidence-based report. This enforces objective grading across all repository aspects, providing concrete findings and remediation guidance that teams can share to align on quality expectations.

Yes, the audit evaluates security and CI/CD by reading a representative sample of at least 20 source files rather than checking every file individually. It enforces strict grading standards by citing concrete evidence from the sampled files for every assessment.

No specific dependencies or environment components are required to run the audit. The only prerequisite is executing the skill from the repository root to rigorously evaluate structure, documentation, architecture, testing, security, reliability, CI/CD, and governance.

Requiring concrete evidence for every grade improvement ensures ruthless, objective, and evidence-based assessments of codebases and processes. This strict grading standard prevents subjective evaluations by tying every finding to specific source files and remediation guidance.