[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A08MC9ERTFGW53T3Z7PESC":3,"skill-same:01M7A08MC9ERTFGW53T3Z7PESC":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7A08MC9ERTFGW53T3Z7PESC","incident-response",null,"Run an incident response workflow covering triage, status updates, mitigation tracking, and postmortems.","meymchen\u002Fskills","meymchen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86772442?v=4","01M7A07YW1B5X4TFJ0S1SRNM7M","Yuming Chen","01M7A07YX3VNGS7DC687B1P7A1",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fincident-response\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: incident-response\ndescription: Run an incident response workflow covering triage, status updates, mitigation tracking, and postmortems.\ndisable-model-invocation: true\nuser-invocable: true\nargument-hint: \"\u003Cincident description or alert>\"\n---\n\n\u003C!-- Adapted by Yuming Chen on 2026-10-04 for personal use and dual-host support. See ..\u002F..\u002FUPSTREAM.md. -->\n\n# Incident Response\n\n> Read [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md) for host invocation, personal use, and optional tools.\n\nManage an incident from detection through postmortem.\n\n## Usage\n\nClaude Code examples are shown below. In Codex, select this plugin's `incident-response` skill or use `$engineering:incident-response` with the same request.\n\n```text\n\u002Fengineering:incident-response \u003Crequest>\n```\n\n## Modes\n\n```text\n\u002Fengineering:incident-response new [description]     # Start a new incident\n\u002Fengineering:incident-response update [status]       # Draft a status update\n\u002Fengineering:incident-response postmortem            # Generate postmortem from incident data\n```\n\nIf the incident phase is not clear from the request or context, ask which phase to use.\n\n## How It Works\n\n```text\n┌─────────────────────────────────────────────────────────────────┐\n│                    INCIDENT RESPONSE                               │\n├─────────────────────────────────────────────────────────────────┤\n│  Phase 1: TRIAGE                                                  │\n│  ✓ Assess severity (SEV1-4)                                     │\n│  ✓ Identify affected systems and users                          │\n│  ✓ Assign roles (IC, comms, responders)                         │\n│                                                                    │\n│  Phase 2: COMMUNICATE                                              │\n│  ✓ Draft internal status update                                  │\n│  ✓ Draft customer communication (if needed)                     │\n│  ✓ Set up war room and cadence                                   │\n│                                                                    │\n│  Phase 3: MITIGATE                                                 │\n│  ✓ Document mitigation steps taken                               │\n│  ✓ Track timeline of events                                      │\n│  ✓ Confirm resolution                                            │\n│                                                                    │\n│  Phase 4: POSTMORTEM                                               │\n│  ✓ Blameless postmortem document                                 │\n│  ✓ Timeline reconstruction                                       │\n│  ✓ Root cause analysis (5 whys)                                  │\n│  ✓ Action items with owners                                      │\n└─────────────────────────────────────────────────────────────────┘\n```\n\nFor a solo project, the maintainer covers the applicable roles. Keep a local timeline; omit war-room setup, paging, and internal updates when there is no team or audience.\n\n## Severity Classification\n\nUse the project's severity policy when available; otherwise treat these as suggested targets.\n\n| Level | Criteria | Response Time |\n| ------- | ---------- | --------------- |\n| SEV1 | Service down, all users affected | Immediate; involve other responders if available |\n| SEV2 | Major feature degraded, many users affected | Within 15 min |\n| SEV3 | Minor feature issue, some users affected | Within 1 hour |\n| SEV4 | Cosmetic or low-impact issue | Next business day |\n\n## Communication Guidance\n\nProvide clear, factual updates at regular cadence. Include: what's happening, who's affected, what we're doing, when the next update is.\n\n## Output — Status Update\n\n```markdown\n## Incident Update: [Title]\n**Severity:** SEV[1-4] | **Status:** Investigating | Identified | Monitoring | Resolved\n**Impact:** [Who\u002Fwhat is affected]\n**Last Updated:** [Timestamp]\n\n### Current Status\n[What we know now]\n\n### Actions Taken\n- [Action 1]\n- [Action 2]\n\n### Next Steps\n- [What's happening next and ETA]\n\n### Timeline\n| Time | Event |\n|------|-------|\n| [HH:MM] | [Event] |\n```\n\n## Output — Postmortem\n\n```markdown\n## Postmortem: [Incident Title]\n**Date:** [Date] | **Duration:** [X hours] | **Severity:** SEV[X]\n**Authors:** [Names] | **Status:** Draft\n\n### Summary\n[2-3 sentence plain-language summary]\n\n### Impact\n- [Users affected]\n- [Duration of impact]\n- [Business impact if quantifiable]\n\n### Timeline\n| Time (UTC) | Event |\n|------------|-------|\n| [HH:MM] | [Event] |\n\n### Root Cause\n[Detailed explanation of what caused the incident]\n\n### 5 Whys\n1. Why did [symptom]? → [Because...]\n2. Why did [cause 1]? → [Because...]\n3. Why did [cause 2]? → [Because...]\n4. Why did [cause 3]? → [Because...]\n5. Why did [cause 4]? → [Root cause]\n\n### What Went Well\n- [Things that worked]\n\n### What Went Poorly\n- [Things that didn't work]\n\n### Action Items\n| Action | Owner | Priority | Due Date |\n|--------|-------|----------|----------|\n| [Action] | [Person] | P0\u002FP1\u002FP2 | [Date] |\n\n### Lessons Learned\n[Key takeaways for the maintainer or team]\n```\n\n## If Connectors Available\n\nIf **~~monitoring** is connected:\n\n- Pull alert details and metrics\n- Show graphs of affected metrics\n\nIf **~~incident management** is connected:\n\n- Create or update incident in PagerDuty\u002FOpsgenie\n- Page on-call responders\n\nIf **~~chat** is connected:\n\n- Post status updates to incident channel\n- Create war room channel\n\n## Tips\n\n1. **Start writing immediately** — Don't wait for complete information. Update as you learn more.\n2. **Keep updates factual** — What we know, what we've done, what's next. No speculation.\n3. **Postmortems are blameless** — Focus on systems and processes, not individuals.\n","\u003C!-- Adapted by Yuming Chen on 2026-10-04 for personal use and dual-host support. See ..\u002F..\u002FUPSTREAM.md. -->\n\n# Incident Response\n\n> Read [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md) for host invocation, personal use, and optional tools.\n\nManage an incident from detection through postmortem.\n\n## Usage\n\nClaude Code examples are shown below. In Codex, select this plugin's `incident-response` skill or use `$engineering:incident-response` with the same request.\n\n```text\n\u002Fengineering:incident-response \u003Crequest>\n```\n\n## Modes\n\n```text\n\u002Fengineering:incident-response new [description]     # Start a new incident\n\u002Fengineering:incident-response update [status]       # Draft a status update\n\u002Fengineering:incident-response postmortem            # Generate postmortem from incident data\n```\n\nIf the incident phase is not clear from the request or context, ask which phase to use.\n\n## How It Works\n\n```text\n┌─────────────────────────────────────────────────────────────────┐\n│                    INCIDENT RESPONSE                               │\n├─────────────────────────────────────────────────────────────────┤\n│  Phase 1: TRIAGE                                                  │\n│  ✓ Assess severity (SEV1-4)                                     │\n│  ✓ Identify affected systems and users                          │\n│  ✓ Assign roles (IC, comms, responders)                         │\n│                                                                    │\n│  Phase 2: COMMUNICATE                                              │\n│  ✓ Draft internal status update                                  │\n│  ✓ Draft customer communication (if needed)                     │\n│  ✓ Set up war room and cadence                                   │\n│                                                                    │\n│  Phase 3: MITIGATE                                                 │\n│  ✓ Document mitigation steps taken                               │\n│  ✓ Track timeline of events                                      │\n│  ✓ Confirm resolution                                            │\n│                                                                    │\n│  Phase 4: POSTMORTEM                                               │\n│  ✓ Blameless postmortem document                                 │\n│  ✓ Timeline reconstruction                                       │\n│  ✓ Root cause analysis (5 whys)                                  │\n│  ✓ Action items with owners                                      │\n└─────────────────────────────────────────────────────────────────┘\n```\n\nFor a solo project, the maintainer covers the applicable roles. Keep a local timeline; omit war-room setup, paging, and internal updates when there is no team or audience.\n\n## Severity Classification\n\nUse the project's severity policy when available; otherwise treat these as suggested targets.\n\n| Level | Criteria | Response Time |\n| ------- | ---------- | --------------- |\n| SEV1 | Service down, all users affected | Immediate; involve other responders if available |\n| SEV2 | Major feature degraded, many users affected | Within 15 min |\n| SEV3 | Minor feature issue, some users affected | Within 1 hour |\n| SEV4 | Cosmetic or low-impact issue | Next business day |\n\n## Communication Guidance\n\nProvide clear, factual updates at regular cadence. Include: what's happening, who's affected, what we're doing, when the next update is.\n\n## Output — Status Update\n\n```markdown\n## Incident Update: [Title]\n**Severity:** SEV[1-4] | **Status:** Investigating | Identified | Monitoring | Resolved\n**Impact:** [Who\u002Fwhat is affected]\n**Last Updated:** [Timestamp]\n\n### Current Status\n[What we know now]\n\n### Actions Taken\n- [Action 1]\n- [Action 2]\n\n### Next Steps\n- [What's happening next and ETA]\n\n### Timeline\n| Time | Event |\n|------|-------|\n| [HH:MM] | [Event] |\n```\n\n## Output — Postmortem\n\n```markdown\n## Postmortem: [Incident Title]\n**Date:** [Date] | **Duration:** [X hours] | **Severity:** SEV[X]\n**Authors:** [Names] | **Status:** Draft\n\n### Summary\n[2-3 sentence plain-language summary]\n\n### Impact\n- [Users affected]\n- [Duration of impact]\n- [Business impact if quantifiable]\n\n### Timeline\n| Time (UTC) | Event |\n|------------|-------|\n| [HH:MM] | [Event] |\n\n### Root Cause\n[Detailed explanation of what caused the incident]\n\n### 5 Whys\n1. Why did [symptom]? → [Because...]\n2. Why did [cause 1]? → [Because...]\n3. Why did [cause 2]? → [Because...]\n4. Why did [cause 3]? → [Because...]\n5. Why did [cause 4]? → [Root cause]\n\n### What Went Well\n- [Things that worked]\n\n### What Went Poorly\n- [Things that didn't work]\n\n### Action Items\n| Action | Owner | Priority | Due Date |\n|--------|-------|----------|----------|\n| [Action] | [Person] | P0\u002FP1\u002FP2 | [Date] |\n\n### Lessons Learned\n[Key takeaways for the maintainer or team]\n```\n\n## If Connectors Available\n\nIf **~~monitoring** is connected:\n\n- Pull alert details and metrics\n- Show graphs of affected metrics\n\nIf **~~incident management** is connected:\n\n- Create or update incident in PagerDuty\u002FOpsgenie\n- Page on-call responders\n\nIf **~~chat** is connected:\n\n- Post status updates to incident channel\n- Create war room channel\n\n## Tips\n\n1. **Start writing immediately** — Don't wait for complete information. Update as you learn more.\n2. **Keep updates factual** — What we know, what we've done, what's next. No speculation.\n3. **Postmortems are blameless** — Focus on systems and processes, not individuals.\n",{"name":5,"description":7,"argument-hint":24,"user-invocable":25,"disable-model-invocation":25},"\u003Cincident description or alert>",true,"main","034f338e49d8ea376e159fafec7e59bf79f55107","plugins\u002Fengineering\u002Fskills\u002Fincident-response","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills","https:\u002F\u002Fgithub.com\u002Fmeymchen","A full-stack AI & CFD engineer","2026-10-16 09:14:33",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add meymchen\u002Fskills --skill incident-response",{"tool":39,"command":40},"bunx","bunx skills add meymchen\u002Fskills --skill incident-response",{"tool":42,"command":43},"pnpm","pnpm dlx skills add meymchen\u002Fskills --skill incident-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fincident-response\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",194,"https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fincident-response\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7A09PZZAC1V90F8PXN278KS","cleanup-merged-branch","Safely clean a merged local branch, reproducible worktree caches, and stale local branches before updating the repository default branch.","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Froutine\u002Fcleanup-merged-branch\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7A09FTDBSMW33ESDA5P9CKK","verify-acceptance-items","Verify a GitHub pull request or GitLab merge request (MR) against the acceptance criteria (验收标准\u002F条件, task-list checkboxes) of the issues it links to, then tick the criteria it proves once the user confirms. Use when asked whether a PR or MR is done or meets its issue, when asked to check off an issue's checkboxes, or right after opening or updating a PR or MR that closes an issue.","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fverify-acceptance-items\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7A09CYZ6M8F4PC8QEBQ4Y1E","update-request-body","Update the title and body of one or more GitHub pull requests or GitLab merge requests (MRs).","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fgit-workflows\u002Fskills\u002Fupdate-request-body\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7A099Q7HVH5ZWCJ76MTFB3V","commit","Create a Git commit from the current changes.","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fgit-workflows\u002Fskills\u002Fcommit\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7A095EK8QKEP2RJHBQZM3W3","commit-push-request","Commit current changes, push the branch, and open a GitHub pull request or GitLab merge request (MR).","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fgit-workflows\u002Fskills\u002Fcommit-push-request\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7A093GR1VP5X5NQQVBAD5RZ","clean-gone","Remove local Git branches whose upstreams are gone, including associated worktrees.","https:\u002F\u002Fgithub.com\u002Fmeymchen\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fgit-workflows\u002Fskills\u002Fclean-gone\u002FSKILL.md",[],[]]