Code Health Degradation and Static Analysis Triage Reporting Framework

Role: Principal Software Quality Architect and Technical Debt Strategist.

Context

• Target codebase repository: {{codebase_repository}}
• Automated static analysis toolchain: {{static_analysis_tooling}}
• Unit and integration coverage baseline: {{test_coverage_baseline}}
• Flaky test rate in CI/CD pipelines: {{flaky_test_ratio}}
• Open static security issues: {{critical_vulnerability_count}}
• Target remediation cycle: {{target_refactoring_sprint}}

Task

Create a comprehensive code health degradation and static analysis triage reporting framework that enables engineering managers to quantify architectural debt, prioritize high-risk code modules, and enforce quality gates across {{codebase_repository}}.

Method

1. Aggregate linting, static analysis, and security scanning findings from {{static_analysis_tooling}}.
2. Map {{critical_vulnerability_count}} security defects against module complexity and cyclomatic thresholds.
3. Evaluate regression vulnerability surface where test coverage drops below {{test_coverage_baseline}}.
4. Measure continuous integration test pipeline friction caused by {{flaky_test_ratio}}.
5. Formulate a risk weighting matrix combining change failure rate, code churn, and test flakiness.
6. Define objective criteria for gating pull requests versus deferring fixes to {{target_refactoring_sprint}}.
7. Design a standardized scorecard format for tracking multi-sprint code health trends across development teams.

Constraints

• MUST require evidence-based risk scoring for every identified code module rather than subjective developer sentiment.
• MUST NOT allow critical security findings from {{critical_vulnerability_count}} to be classified as low-priority technical debt.
• Remediation roadmaps MUST fit within the operational capacity of {{target_refactoring_sprint}}.
• The scorecard framework must be modular and applicable across both monolithic and service-oriented repositories.

Output format

1. Code Health Executive Scorecard (structured metrics block with coverage, flakiness, and security metrics).
2. Architectural Debt Risk Matrix (markdown table: Module Path, Risk Tier, Cyclomatic Burden, Target Action).
3. Quality Gate Decision Tree (conditional evaluation steps for pull request merges).
4. Sprint Remediation Backlog Template (standardized schema for {{target_refactoring_sprint}} issues).

Self-review

• Verify test coverage thresholds from {{test_coverage_baseline}} and {{flaky_test_ratio}} are directly linked to pipeline gating rules.
• Ensure all 4 designated output sections are explicitly defined.
• Confirm the evaluation logic enforces strict differentiation between security debt and style linting.