tech-debt-ci-review

To audit technical debt causing CI instability, run a phase-driven inventory that explores workflows, dependencies, and test suites in parallel to surface brittle tooling and flaky-test risks. This generates a comprehensive CI stability report.

Identify flaky tests and verification gaps in a large codebase through parallel exploration of test coverage and tooling. This process validates candidates with exact file paths and lines of evidence to avoid false positives.

A CI pipeline audit inventories workflows, dependencies, and test coverage to map risk surfaces across a repository. You need one when deep technical debt threatens PR green status by hiding failures and slowing feedback loops.

Yes, the CI debt audit validates candidates by documenting exact file paths and lines of evidence. This precision satisfies phased inventory requirements and prevents false positives during the repository workflow analysis.

The best way to keep PRs green without unnecessary feature work is to surface CI debt, flaky tests, and verification gaps through an audit checklist. This provides actionable guidance for tooling and test suite remediation.