agentleFS
kryptophonikkryptophonik/SRE-Skills/skills/sre-change-safety/SKILL.md

sre-change-safety

Skill4 starsChanged 23 days agoMITView on GitHub

Use before, during or right after a deploy, migration or infra change: risk score, freeze and error-budget check, canary/progressive rollout, rollback plan, post-deploy verification.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.

    line 12
  2. Distinctive:

    No tested rollback plan, or irreversible step without backup.

    line 34
  3. Distinctive:

    No owner watching during and after rollout.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Change Safety

Safety gates (REQUIRED)

  1. Read-only diagnosis first.
  2. Propose each change with risk (low/med/high) and reversibility.
  3. Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
  4. Act only as approved, verify, and stop and escalate if anything gets worse.

Full rules: sre-safety-gates. Read-only MCP setup: sre-safety-gates/references/mcp.md.

Risk score

FactorLow (1)Med (2)High (3)
Blast radiusone service, canaryone region / many usersglobal / shared infra
Reversibilityinstant rollbackrollback with effortirreversible (data/schema migration, deletes)
Noveltyroutine, automatednew config pathfirst time / manual
Timingbusiness hours, staffedlate dayFriday night, holiday, peak
ObservabilitySLO + alerts cover itpartialblind

Total 5–7 low, 8–11 med (peer review + canary), 12–15 high (approval from owner, staffed window, explicit rollback test).

No-go rules

  • Change freeze in effect without an approved exception.
  • Error budget exhausted for the affected service (only reliability fixes go out).
  • Active SEV-1/SEV-2 on the same service or shared dependency. Exception: changes that reduce that incident's impact (roll back or revert to the last known-good version, turn a feature flag off, scale up) may go ahead once the IC, or the single responder acting as IC, approves them; log each one in the incident timeline. Anything new still waits until the incident is resolved.
  • No tested rollback plan, or irreversible step without backup.
  • No owner watching during and after rollout.

Workflow

  1. Describe the change: what, where, why, linked PR/plan.
  2. Score risk and check no-go rules.
  3. Pre-checks (read-only): CI green, terraform plan reviewed (sre-terraform), dashboards and SLOs healthy, dependencies healthy.
  4. Plan rollout: canary (1–5%) -> 25% -> 50% -> 100%, with bake time and gate metrics (error ratio, p95 latency, saturation).
  5. Get approval for the plan.
  6. Roll out step by step; check gates at each step. For Terraform, apply only the exact saved plan that was reviewed and approved.
  7. Roll back immediately if a gate fails (follow sre-remediation-actions).
  8. Verify 15–30 min after 100%; record result.

Useful read-only commands

kubectl --context <ctx> -n <ns> rollout status deployment/<name> --timeout=60s
kubectl --context <ctx> -n <ns> rollout history deployment/<name>
kubectl argo rollouts --context <ctx> -n <ns> get rollout <name>   # Argo Rollouts plugin
terraform plan -input=false -out=<plan-file> && terraform show -no-color <plan-file>   # apply only this exact reviewed plan

Change record template

# Change: [title]
- **Owner / approver:** [names]
- **Risk score:** [n] ([low|med|high])
- **Window:** [start–end, timezone]
- **Rollout plan:** [steps + gate metrics]
- **Rollback plan:** [exact steps, tested? yes/no]
- **Result:** [success / rolled back — evidence links]

Output

  • Change record with risk score, go/no-go decision, rollout and rollback plan, verification result

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.