[ngpayyappilly]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot. (Not tested in Copilot; see "Testing and AI disclosure" below for what was and was not verified.)
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

Improves the existing incident-postmortem skill rather than adding a duplicate:

• Google SRE format: the output follows the Google SRE post-mortem template (Summary, Impact, Root Causes, Trigger, Detection, Resolution, Action Items, Lessons Learned incl. "Where we got lucky", Timeline, Supporting Information).
• Fishbone before 5 Whys: candidate causes are brainstormed across six categories and marked confirmed / suspected / ruled out. Separate 5 Whys chains then drill the strongest branches, so an incident can yield more than one root cause.
• User-supplied inputs: the skill gathers metadata, impact, timeline, evidence and output format from the user, and must not invent details (unknowns become open questions).
• Typed action items: each is tagged Detect / Mitigate / Prevent, with owner, tracking ticket, due date and priority.
• Output formats: Markdown by default; HTML, DOCX (via the existing md-to-docx skill) or PDF on request.
• The template and a worked example moved into references/ to keep SKILL.md focused.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Testing and AI disclosure

This PR was authored by an AI agent (Claude Code) at a human contributor's request and direction, hence the 🤖🤖🤖 title marker.

What was verified, and how:

• npm run skill:validate and npm run build pass; the repo's CI checks pass.
• Format and conversion path: I wrote a post-mortem for a made-up, clearly labelled scenario (an expired internal mTLS certificate causing a 38-minute order outage) by following the skill's process and references/postmortem-template.md: inputs, timeline, fishbone, two 5 Whys chains from different categories, and Detect/Mitigate/Prevent action items. I then converted it with the existing md-to-docx skill. The .docx generated without errors and contains all five tables and the fishbone tree.

What was NOT verified:

• The skill has not been run inside GitHub Copilot, and no human has run it on a real incident yet. Because I followed the skill by hand rather than letting a fresh agent load it, this shows the template and conversion work, not that an agent reliably follows the process.
• HTML and PDF output are described in the skill but were not exercised.

Additional Notes

The skill name and trigger phrases are unchanged, so existing users are unaffected. docs/README.skills.md was regenerated with npm run build.

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

🤖 Generated with Claude Code

[github-actions]

🚦 Submission status: 💬 Review in progress

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier

• Adds 2 file(s), e.g. skills/incident-postmortem/references/fishbone-example.md
• Changes 439 lines (low-risk limit is 40)

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Skill validation	✅ Passed	Passed · logs
Skill lint (vally)	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs

Review

• Approvals: 0/1
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 1 more approval(s)
• No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 25cc28c · gate run · This comment is maintained automatically — see submission gate docs.}

[github-actions]

🔒 PR Risk Scan Results

Scanned 3 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔍 Vally Lint Results

✅ All checks passed

Scope	Checked
Skills	1
Agents	0
Total	1

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	✅ incident-postmortem (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️	✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️	1 skill(s) linted, 1 passed

Full linter output

### Linting skills/incident-postmortem
✅ incident-postmortem (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

[aaronpowell]

Thanks for improving the existing skill. The strongest parts are the no-fabrication rule, cause status labels, evidence-backed 5 Whys and typed action items. Before merge:

1. DOCX path (Step 8): node skills/md-to-docx/scripts/md-to-docx.mjs only works inside an awesome-copilot checkout. Make it conditional on md-to-docx being installed, or drop DOCX from the defaults.
2. Trim: cut untested HTML/PDF rows, collapse Step 5 into the template, remove Common Mistakes rows that repeat the Process, and link the template rather than re-listing sections in Step 7.
3. Validation: run the skill once in GitHub Copilot with it loaded on a realistic incident and note the result.

A short note on compatibility for existing users of the #2019 template would also help.

[ngpayyappilly]

@aaronpowell Thanks for the review and I'll address the review comments soon and request for further reviews.