AI-ASSISTED CHANGE CONTROL (PR + RELEASE) — TEMPLATE

Use this as:
1).github/pull_request_template.md
2) A release checklist for high-risk services

---
PULL REQUEST TEMPLATE

Title: <clear, specific>
Linked issue/ticket: <URL>
Service/component: <name>
Risk level (pick one): Low / Medium / High

1) Intent (2–5 sentences)
- What problem does this change solve?
- What user/system behavior should be different after merge?

2) Approach (brief)
- What did you change at a high level?
- What alternative did you reject, and why?

3) AI involvement (be explicit)
- Tools used (e.g., Copilot, Cursor, ChatGPT, Claude, Gemini):
- What parts were AI-generated (tests, refactor, new module, docs, etc.)?
- What parts did you manually author or heavily edit?

4) Proof (link or paste evidence)
- CI run link / status:
- Tests added or updated (name them):
- If behavior/perf changed: link to dashboard query, trace, or benchmark method:

5) Invariants + failure modes
- What must remain true after this change? (e.g., auth rules, idempotency, backward compatibility)
- How could this fail in production?

6) Rollback plan
- How do we revert quickly? (toggle, revert commit, config change)
- Any data migrations or irreversible steps?

7) Security & data handling
- Confirm: no secrets or customer data were pasted into consumer tools.
- Any new dependencies? If yes, why are they acceptable?

Reviewer checklist (for reviewers to use)
- I can explain the change and its risks without reading chat logs.
- The proof matches the intent (tests/metrics validate the claim).
- The diff is reasonably scoped; risky refactors are split.

---
RELEASE CHECKLIST (use for Medium/High risk)

Pre-release
- Owner on-call identified:
- Feature flag / staged rollout plan:
- Metrics to watch (errors, latency, saturation):
- Alert coverage verified:

During release
- Deploy initiated by:
- Canary/stage result observed for:
- Any anomalies noted:

Post-release (timebox: 30–60 minutes)
- Key dashboards checked:
- Support queue / user reports checked:
- Decision: continue rollout / pause / rollback
- Notes recorded in incident/release log:

Rule: If you can’t name the owner and the proof, you don’t ship.