swe:incident-followup-audit SKILL.md skillA
swe:incident-followup-audit from ckorhonen/swe-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ckorhonen/swe-skills/swe:incident-followup-audit@git:20260404.9370c32Pins git:20260404.9370c32 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ckorhonen/swe-skills
- Path
skills/incident-followup-audit/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260404.9370c32, committed Apr 4, 2026
- Size
- 5,781 bytes
- Repository stars
- 3
- License
- MIT
Audits post-incident engineering follow-through after a sev or incident to verify whether the durable follow-up happened: regression tests, monitors, docs, runbooks, ownership updates, tickets, rollback learnings, and remaining backlog. Use when a user asks whether incident follow-up is complete, what still needs to be done after a postmortem, or how to close the engineering loop. Do NOT use for live incident response, root-cause analysis, or a generic bug hunt unrelated to an incident.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SWE Incident Follow-up Audit ## What This Skill Does Use this skill to check whether the engineering work that should happen after an incident actually happened. The goal is not to explain the incident itself. The goal is to answer: - What follow-up work is done - What follow-up work is missing - What follow-up work is still uncertain - What remains in the smallest sensible backlog The skill should stay evidence-led and conservative. If follow-up cannot be proven, mark it as unknown rather than filling in the gap. ## When To Use Use this skill when the user wants to: - Audit postmortem follow-through after a sev or production incident - Check whether regression tests, monitors, runbooks, or docs were added - See whether ownership, tickets, or rollback learnings were captured - Review what is still left to do before the incident can be considered fully closed ## Do Not Use Do not use this skill for: - Live incident response or war-room triage - Root-cause analysis of the incident itself - Generic code review or bug hunting with no incident context - Broad cleanup work that is not tied to a concrete incident or postmortem ## Inputs To Confirm Confirm or infer: …
Read the whole file at its exact version.
How to install
mdr add ckorhonen/swe-skills/swe:incident-followup-audit@sha256:0f21ac2cd3ec7d9cThe line at the top of this page pins the label git:20260404.9370c32, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_grukxu7dgpxzpljk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 4, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5781 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ckorhonen/swe-skills · 3 stars · license MIT · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_grukxu7dgpxzpljk GET https://markdownregistry.com/api/v1/resolve?ref=ckorhonen/swe-skills/swe:incident-followup-audit GET https://markdownregistry.com/api/v1/blob/0f21ac2cd3ec7d9c48ab2bcf8b21890d2d5829703d0a9a1836cc91869d413ed7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.