standardize-repo

To apply standardized DevOps tooling and CI/CD workflows to an existing repository, use Copier to render the harmon-init template. This retrofits your project with consistent git hooks, Taskfile task runners, and automated security scanning without manually copying files.

Configuration drift auditing compares your repository against a canonical standards catalog to identify missing hooks, workflows, or configuration gaps. It ensures your project maintains consistent DevOps tooling and security practices over time.

Yes, you need Copier, GitHub CLI, Task, and yq installed locally to scaffold a new project with harmon-init. These dependencies execute verified, non-interactive template renders and verification gates during standardization.

Yes, you can retrofit an existing project with git history using Copier templates. The standardization process applies the harmon-init template directly to existing repositories, adding standardized infrastructure without losing your current commit history.

The best way to standardize repository security configurations across multiple projects is by applying a Copier template like harmon-init. It enforces a canonical standards catalog to eliminate manual setup overhead and ensure consistent security practices.

Repository standardization template renders fail during verification gates when local dependencies like Copier, Task, yq, or GitHub CLI are missing or misconfigured. The process requires these tools to execute verified, non-interactive renders successfully.