Skip to content

hoangminhung/devops-ai-kit / claude/skills/infra-docs

infra-docs

Verified

Write infrastructure documentation based on real evidence — change records of what was changed and why, concept/learning notes that explain how a tool or stack works, runbooks for operating a component, ADRs for architecture decisions, and blameless postmortems. Use whenever the user wants to document something, write handover or onboarding material, explain how a technology works for learning or for new team members, record a change, or write a runbook, ADR or postmortem.

FileKindSize
SKILL.mdskill md5.0 KB
templates/adr.mdmarkdown1.1 KB
templates/change-record.mdmarkdown1.4 KB
templates/concept-note.mdmarkdown1.7 KB
templates/postmortem.mdmarkdown1.2 KB
templates/runbook.mdmarkdown1.4 KB

templates/postmortem.md

View on GitHub
# Postmortem: <incident summary> (<YYYY-MM-DD>)

- **Severity:** SEV1 | SEV2 | SEV3
- **Impact window:** <start> → <end> (<total duration>)
- **Author / responders:**
- **Status:** Draft | Reviewed | Actions done
- **Principle:** blameless — describe the system and the decisions, do not blame a person.

## 1. Summary

<3–5 lines: what happened, who was affected, how it was fixed.>

## 2. Impact

- Users / services:
- Data (lost / wrong / delayed):
- SLO budget used:

## 3. Timeline

| Time | Event | Source (alert / log / person) |
|---|---|---|

## 4. Root cause

<Chain of causes (5 whys). Separate the direct cause from the contributing conditions.>

## 5. Detection & response

- How was it detected, and after how long? How should it have been detected?
- What helped us fix it fast? What slowed us down?

## 6. Actions

| Action | Type (prevent / detect / reduce impact) | Owner | Due | Status |
|---|---|---|---|---|

## 7. Lessons for the AI rules (devops-ai-kit)

<If the AI was involved: which rule / skill / permission should be added or changed so this does not happen again. Name the exact file and the suggested content.>

## 8. References

- Related change record / PR:
- Dashboards / queries used in the investigation:
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall