check-setup-against-standards

To audit a repository against engineering standards, run a structured read-only compliance check that identifies configuration, tooling, and structural gaps. It generates categorized gap reports with severity ratings and remediation hints, preventing rework during team reviews.

Checking dev environment compliance involves validating repository configurations against predefined developer standards. This process inspects dev container setup, dependency management, and folder structure, outputting a prioritized list of compliance gaps with clear fix recommendations.

Yes, you can validate a new repository for AWS data engineering standards without modifying files. The compliance audit runs as a read-only check against the repository, identifying missing tooling and structural requirements while leaving the codebase untouched.

Generating a gap report for missing linting tooling and git hygiene configurations requires auditing the repository against canonical standards. The audit groups findings by Environment, Tooling, Structure, and Git hygiene, assigning FAIL, WARN, or SKIP severity ratings.

Yes, repo compliance checking requires access to the shared audit.py script and the canonical STANDARDS.md file from the sibling set-up-env skill. These dependencies are necessary to execute the structured audit and generate accurate gap reports with remediation guidance.