project-alignment

A project configuration audit reviews CLAUDE.md, memory files, Git history, and test coverage data to identify missing tests and security gaps. It then generates a prioritized roadmap with concrete items like CI/CD enhancements and security checks to resolve the detected inconsistencies.

You should run a project alignment check during repository onboarding, after applying global configuration changes, or whenever you request a quality audit. This ensures your project stays synchronized with global standards and prevents missing tests or security gaps from reaching production.

To generate a todo list for CI/CD and test coverage gaps, execute a gap analysis on your repository's Git history and configuration files. This produces a prioritized tasks/todo.md file containing concrete items like E2E suite targets, security audits, and tooling enhancements.

Yes, the alignment audit requires access to the project's CLAUDE.md and memory files. It also needs the ability to execute Git commands and run security or performance audit tools to accurately read test coverage metrics and analyze recent repository history.

The best way to identify missing security checks and untested user flows is to perform a comprehensive gap analysis. This process reads test coverage metrics and recent Git history to pinpoint security vulnerabilities and map out user flows that lack proper test coverage.