ai-standardize-repo

You can standardize repository configurations by running the ai-tools standardize pipeline against a target repo path to audit and align pipelines, tooling, and governance with canonical policies. It detects drift across dotfiles, pre-commit hooks, Renovate, and release settings.

Yes, you can detect configuration drift safely by using the dry-run mode to compute a full standardization plan without mutation. It reports drift statuses per section across pipelines, pre-commit hooks, Renovate, and GitHub rulesets before prompting for action.

The best way to enforce canonical policies for GitHub rulesets and OIDC is to apply the ai-gh config and rulesets standardization steps. This validates your repository governance settings against a canonical contract and applies deterministic writes.

Yes, this repository standardization tool explicitly supports both library and service repos. It handles standardization workflows tailored to each type, applying canonical changes across pipelines, release settings, and governance configurations.

Yes, you can run standardization for a specific area instead of the full repository by using per-area single-step runs. This allows you to target individual sections like pipelines, Renovate, or release configs independently.

You should use dry-run mode for repo standardization to safely audit configurations and compute a 10-step plan without mutating files. It enables safe, auditable AI-assisted workflows by validating against the canonical contract before applying any changes.