evidence-based-development

Evidence-based code review enforces verifiable findings by requiring exact file:line citations for all behavioral claims. It applies an assertion-evidence-verified pattern to pull request analysis, ensuring recommendations are grounded in source files rather than unsourced confidence.

The assertion-evidence pattern is a reproducible workflow where every non-trivial claim is stated, supported with file:line evidence, and then verified by reading code or running tests. This traceable process ensures development decisions rely on cited facts instead of assumptions.

Prioritize code review findings by classifying issues as P1, P2, or P3. This severity ranking tells reviewers and engineers what regressions must be fixed immediately versus later, enabling a findings-first summary with targeted fixes and verification steps.

Yes, you can use file:line citations to verify behavioral claims across repositories and PR workflows. The evidence-first approach requires reading source files and citing exact locations, making all development recommendations traceable and reviewable.

Evidence-based development does not require specific testing frameworks; it verifies claims through direct code inspection or running existing tests. The workflow focuses on reading source files and citing exact file:line locations to validate behavioral assertions during code review.