Source RCA and PR Remediation Reference
Connect source repositories when production symptoms frequently correlate to code, IaC, pipeline, or deployment changes.
Investigation Contract
- Start from incident/alert symptoms, resource scope, and deployment timeline.
- Correlate source changes, commits, PRs, IaC files, and pipeline runs.
- Provide file:line references where available.
- Separate evidence, hypotheses, and recommendations.
- Prefer issue/PR draft handoff over direct remediation.
- Never merge, deploy, or apply production fixes automatically.
PR Readiness
A remediation PR draft needs:
- incident link and affected service
- root-cause evidence
- minimal change scope
- tests and validation
- security/secrets review
- rollback or roll-forward plan
- owner and reviewer
- deployment safety notes