[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754P6CM3P7PA8JBH2WMXE6Y":3,"skill-same:01M754P6CM3P7PA8JBH2WMXE6Y":57},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M754P6CM3P7PA8JBH2WMXE6Y","x-handle-incident",null,"Guides incident response with severity-based checklists, communication templates, and postmortem triggers. Interactive guide for SEV1-SEV4 incidents covering classification, response coordination, and action item tracking.","review-bench\u002Federcnj_ia-dev-environment","review-bench","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286778065?v=4","01M7517F9NTEPDZDAXJBR30FWT","ReviewBench","01M7517FAC9F4P7TGWCNJ8VYVW",0,"MIT","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-fintech-pci\u002F.claude\u002Fskills\u002Fx-handle-incident\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-handle-incident\ndescription: \"Guides incident response with severity-based checklists, communication templates, and postmortem triggers. Interactive guide for SEV1-SEV4 incidents covering classification, response coordination, and action item tracking.\"\nuser-invocable: true\nargument-hint: \"[severity SEV1|SEV2|SEV3|SEV4] [--postmortem] [--notify]\"\ncontext-budget: medium\nallowed-tools: Read, Write, Bash, Grep, Glob, Agent\nrequires-capabilities: []\n---\n\n## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: Incident Response\n\n## Purpose\n\nProvides an interactive incident response guide for {{PROJECT_NAME}} that walks the team through the complete process from detection to resolution. Classifies severity, loads severity-specific checklists, coordinates communication, triggers postmortems, and tracks action items.\n\n## Triggers\n\n- `\u002Fx-handle-incident` — start interactive severity classification\n- `\u002Fx-handle-incident SEV1` — start SEV1 critical incident response\n- `\u002Fx-handle-incident SEV2 --postmortem` — SEV2 incident with postmortem generation\n- `\u002Fx-handle-incident SEV3 --notify` — SEV3 incident with communication templates\n- `\u002Fx-handle-incident SEV1 --postmortem --notify` — full incident response workflow\n\n## Parameters\n\n| Parameter | Type | Default | Description |\n|-----------|------|---------|-------------|\n| `severity` | positional | (interactive) | Severity level: `SEV1`, `SEV2`, `SEV3`, or `SEV4` |\n| `--postmortem` | boolean | `false` | Generate postmortem document (auto-enabled for SEV1\u002FSEV2) |\n| `--notify` | boolean | `false` | Generate communication templates for all channels |\n\n## Workflow\n\n```\n1. CLASSIFY     -> Analyze impact description and classify severity (SEV1-SEV4)\n2. LOAD         -> Load severity-specific checklist from SRE Practices KP\n3. GUIDE        -> Conduct team through Detection -> Triage -> Mitigation -> Resolution\n4. COMMUNICATE  -> Generate communication templates (status page, Slack, email)\n5. POSTMORTEM   -> Generate postmortem document from template (SEV1\u002FSEV2 or --postmortem)\n6. TRACK        -> Register action items with owners and deadlines\n```\n\n### Step 1 — Classify Severity\n\nIf severity is provided as argument, validate and use directly. If omitted, ask the user about the impact and suggest classification.\n\n| Severity | Label | Criteria | Response Time | Update Frequency |\n|----------|-------|----------|---------------|------------------|\n| **SEV1** | Critical | Total service outage, significant financial loss, data breach affecting all users | 15 min | Every 30 min |\n| **SEV2** | High | Major feature unavailable, severe performance degradation, large user impact | 30 min | Every 1 hour |\n| **SEV3** | Medium | Minor feature impacted, workaround available, limited user impact | 4 hours | Every 4 hours |\n| **SEV4** | Low | Cosmetic issue, minimal user impact, no business impact | Next business day | Daily |\n\n**Severity Decision Criteria:**\n\n- **User Impact**: How many users are affected? Is it all users or a subset?\n- **Financial Impact**: Is there direct revenue loss or potential financial liability?\n- **Data Impact**: Is there data loss, corruption, or unauthorized access?\n- **Scope**: Is the issue isolated or widespread across regions\u002Fservices?\n\n### Step 2 — Load Checklist\n\nLoad the severity-specific checklist from the SRE Practices knowledge pack (`knowledge\u002Fsre-practices\u002F`). Each severity level has different response requirements:\n\n**SEV1 — Critical Checklist:**\n\n- [ ] Incident Commander assigned within 5 minutes\n- [ ] Response team assembled (engineering, on-call, management)\n- [ ] Communication channel created (war room \u002F bridge call)\n- [ ] Initial status page update published\n- [ ] Executive stakeholders notified within 15 minutes\n- [ ] All hands on deck — pull in additional engineers as needed\n\n**SEV2 — High Checklist:**\n\n- [ ] On-call engineer acknowledged within 10 minutes\n- [ ] Secondary engineer engaged if needed\n- [ ] Communication channel created\n- [ ] Status page update published within 30 minutes\n- [ ] Engineering manager notified\n\n**SEV3 — Medium Checklist:**\n\n- [ ] On-call engineer acknowledged within 1 hour\n- [ ] Workaround documented and communicated\n- [ ] Ticket created for permanent fix\n- [ ] Status page updated if user-facing\n\n**SEV4 — Low Checklist:**\n\n- [ ] Ticket created with appropriate priority\n- [ ] Assigned to next sprint or backlog\n- [ ] No immediate response required\n\n### Step 3 — Guide Response\n\nConduct the team through the incident response flow. Use the `sre-engineer` agent via Agent tool for reliability expertise and validation.\n\n#### Detection\n\n- Identify the alert source (monitoring, user report, automated test)\n- Record alert timestamp and affected service(s)\n- Confirm initial severity assessment\n\n#### Triage\n\n- Determine root cause hypothesis\n- Identify blast radius (affected services, users, regions)\n- Assign roles: Incident Commander (SEV1\u002FSEV2), Communication Lead, Technical Lead\n\n#### Mitigation\n\n- Apply immediate mitigation (rollback, feature flag, scaling, failover)\n- Verify mitigation effectiveness\n- Document mitigation steps taken\n\n#### Resolution\n\n- Implement permanent fix\n- Verify resolution across all affected components\n- Confirm service restoration to normal operation\n- Update status page with resolution notice\n\n### Step 4 — Communicate\n\nGenerate communication templates based on severity and channels. Frequency varies by severity level.\n\n#### Status Page Template\n\n```markdown\n**[INVESTIGATING\u002FIDENTIFIED\u002FMONITORING\u002FRESOLVED]** — {{PROJECT_NAME}}\n\n**Impact:** [Description of user-facing impact]\n**Affected Services:** [List of affected services]\n**Current Status:** [What we know and what we are doing]\n**Next Update:** [Time of next update based on severity]\n```\n\n#### Slack\u002FTeams Internal Update Template\n\n```markdown\n:rotating_light: **Incident Update — [SEV level]**\n**Service:** [affected service]\n**Impact:** [description]\n**Status:** [Investigating\u002FMitigating\u002FResolved]\n**IC:** [Incident Commander name]\n**Timeline:**\n- [HH:MM] [Event description]\n**Next Steps:** [what happens next]\n**Next Update:** [time]\n```\n\n#### Email Stakeholder Notification Template\n\n```markdown\nSubject: [SEV level] Incident — [Brief description]\n\nDear Stakeholders,\n\nWe are currently experiencing [description of the issue]\naffecting [scope of impact].\n\n**Severity:** [SEV1\u002FSEV2\u002FSEV3\u002FSEV4]\n**Impact:** [User-facing impact description]\n**Status:** [Current status]\n**ETA for Resolution:** [Estimate or \"Under investigation\"]\n\nWe will provide updates every [frequency based on severity].\n\nBest regards,\n[Team Name]\n```\n\n**Update Frequency by Severity:**\n\n| Severity | Update Frequency | Channels |\n|----------|-----------------|----------|\n| SEV1 | Every 30 min | Status Page, Slack, Email |\n| SEV2 | Every 1 hour | Status Page, Slack, Email |\n| SEV3 | Every 4 hours | Status Page, Slack |\n| SEV4 | Daily | Slack |\n\n### Step 5 — Postmortem\n\nIf `--postmortem` flag is provided, or severity is SEV1 or SEV2, generate a postmortem document from the `_TEMPLATE-POSTMORTEM.md` template.\n\n**Postmortem is triggered when:**\n\n- Severity is SEV1 (always)\n- Severity is SEV2 (always)\n- `--postmortem` flag is explicitly provided (any severity)\n\n**Postmortem document is pre-filled with:**\n\n- Incident timeline from the response flow\n- Severity classification and impact assessment\n- Mitigation and resolution steps taken\n- Participants and their roles\n- Action items identified during the response\n\nIf the postmortem template is not available, generate an inline postmortem with the basic structure:\n\n```markdown\n# Postmortem — [Incident Title]\n\n## Incident Summary\n| Field | Value |\n|-------|-------|\n| Severity | [SEV level] |\n| Date | [Date] |\n| Duration | [Duration] |\n| Affected Services | [Services] |\n\n## Timeline\n[Pre-filled from incident response]\n\n## Root Cause Analysis\n[To be completed]\n\n## Action Items\n[Pre-filled from tracked items]\n\n## Lessons Learned\n[To be completed]\n```\n\n### Step 6 — Track Action Items\n\nRegister all action items identified during the incident response. Each action item includes:\n\n| Field | Description |\n|-------|-------------|\n| ID | Sequential identifier (AI-001, AI-002, ...) |\n| Description | What needs to be done |\n| Owner | Person responsible |\n| Deadline | Target completion date |\n| Priority | HIGH \u002F MEDIUM \u002F LOW |\n| Status | OPEN \u002F IN_PROGRESS \u002F DONE |\n\n**Output format:**\n\n```markdown\n## Action Items\n\n| ID | Description | Owner | Deadline | Priority | Status |\n|----|-------------|-------|----------|----------|--------|\n| AI-001 | [description] | [owner] | [date] | HIGH | OPEN |\n| AI-002 | [description] | [owner] | [date] | MEDIUM | OPEN |\n```\n\n## Severity Definitions\n\n| Severity | Label | Description | Response Time | Update Frequency | Postmortem Required |\n|----------|-------|-------------|---------------|------------------|---------------------|\n| **SEV1** | Critical | Total service outage, significant financial loss, data breach | 15 min | 30 min | Yes (always) |\n| **SEV2** | High | Major feature unavailable, degraded experience for many users | 30 min | 1 hour | Yes (always) |\n| **SEV3** | Medium | Minor feature impacted, workaround available | 4 hours | 4 hours | Only if --postmortem |\n| **SEV4** | Low | Cosmetic issue, minimal impact | Next business day | Daily | Only if --postmortem |\n\n## Communication Templates\n\nSee Step 4 above for complete templates per channel (Status Page, Slack\u002FTeams, Email) and update frequency per severity level.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Severity not provided | Ask the user about the impact and suggest classification based on description |\n| Invalid severity (e.g., SEV5) | Reject with message: \"Invalid severity. Use SEV1, SEV2, SEV3, or SEV4\" |\n| `--postmortem` without template | Generate inline postmortem with basic structure |\n| No Incident Commander available | Assign the requesting user as IC and recommend finding a replacement |\n| Incomplete information | Proceed with available data, note gaps in postmortem |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-troubleshoot-operations | called-by | Escalates to this skill when an issue becomes a production incident |\n| sre-engineer (agent) | calls | Delegates reliability expertise and checklist validation via Agent tool |\n| sre-practices (KP) | reads | References `knowledge\u002Fsre-practices\u002F` for incident management processes |\n\n- Uses `_TEMPLATE-POSTMORTEM.md` for postmortem document generation. Fallback: inline postmortem with basic structure when template is absent.\n- Uses `_TEMPLATE-INCIDENT-RESPONSE.md` for severity classification reference\n- Can be used standalone or as part of on-call response workflow\n","## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: Incident Response\n\n## Purpose\n\nProvides an interactive incident response guide for {{PROJECT_NAME}} that walks the team through the complete process from detection to resolution. Classifies severity, loads severity-specific checklists, coordinates communication, triggers postmortems, and tracks action items.\n\n## Triggers\n\n- `\u002Fx-handle-incident` — start interactive severity classification\n- `\u002Fx-handle-incident SEV1` — start SEV1 critical incident response\n- `\u002Fx-handle-incident SEV2 --postmortem` — SEV2 incident with postmortem generation\n- `\u002Fx-handle-incident SEV3 --notify` — SEV3 incident with communication templates\n- `\u002Fx-handle-incident SEV1 --postmortem --notify` — full incident response workflow\n\n## Parameters\n\n| Parameter | Type | Default | Description |\n|-----------|------|---------|-------------|\n| `severity` | positional | (interactive) | Severity level: `SEV1`, `SEV2`, `SEV3`, or `SEV4` |\n| `--postmortem` | boolean | `false` | Generate postmortem document (auto-enabled for SEV1\u002FSEV2) |\n| `--notify` | boolean | `false` | Generate communication templates for all channels |\n\n## Workflow\n\n```\n1. CLASSIFY     -> Analyze impact description and classify severity (SEV1-SEV4)\n2. LOAD         -> Load severity-specific checklist from SRE Practices KP\n3. GUIDE        -> Conduct team through Detection -> Triage -> Mitigation -> Resolution\n4. COMMUNICATE  -> Generate communication templates (status page, Slack, email)\n5. POSTMORTEM   -> Generate postmortem document from template (SEV1\u002FSEV2 or --postmortem)\n6. TRACK        -> Register action items with owners and deadlines\n```\n\n### Step 1 — Classify Severity\n\nIf severity is provided as argument, validate and use directly. If omitted, ask the user about the impact and suggest classification.\n\n| Severity | Label | Criteria | Response Time | Update Frequency |\n|----------|-------|----------|---------------|------------------|\n| **SEV1** | Critical | Total service outage, significant financial loss, data breach affecting all users | 15 min | Every 30 min |\n| **SEV2** | High | Major feature unavailable, severe performance degradation, large user impact | 30 min | Every 1 hour |\n| **SEV3** | Medium | Minor feature impacted, workaround available, limited user impact | 4 hours | Every 4 hours |\n| **SEV4** | Low | Cosmetic issue, minimal user impact, no business impact | Next business day | Daily |\n\n**Severity Decision Criteria:**\n\n- **User Impact**: How many users are affected? Is it all users or a subset?\n- **Financial Impact**: Is there direct revenue loss or potential financial liability?\n- **Data Impact**: Is there data loss, corruption, or unauthorized access?\n- **Scope**: Is the issue isolated or widespread across regions\u002Fservices?\n\n### Step 2 — Load Checklist\n\nLoad the severity-specific checklist from the SRE Practices knowledge pack (`knowledge\u002Fsre-practices\u002F`). Each severity level has different response requirements:\n\n**SEV1 — Critical Checklist:**\n\n- [ ] Incident Commander assigned within 5 minutes\n- [ ] Response team assembled (engineering, on-call, management)\n- [ ] Communication channel created (war room \u002F bridge call)\n- [ ] Initial status page update published\n- [ ] Executive stakeholders notified within 15 minutes\n- [ ] All hands on deck — pull in additional engineers as needed\n\n**SEV2 — High Checklist:**\n\n- [ ] On-call engineer acknowledged within 10 minutes\n- [ ] Secondary engineer engaged if needed\n- [ ] Communication channel created\n- [ ] Status page update published within 30 minutes\n- [ ] Engineering manager notified\n\n**SEV3 — Medium Checklist:**\n\n- [ ] On-call engineer acknowledged within 1 hour\n- [ ] Workaround documented and communicated\n- [ ] Ticket created for permanent fix\n- [ ] Status page updated if user-facing\n\n**SEV4 — Low Checklist:**\n\n- [ ] Ticket created with appropriate priority\n- [ ] Assigned to next sprint or backlog\n- [ ] No immediate response required\n\n### Step 3 — Guide Response\n\nConduct the team through the incident response flow. Use the `sre-engineer` agent via Agent tool for reliability expertise and validation.\n\n#### Detection\n\n- Identify the alert source (monitoring, user report, automated test)\n- Record alert timestamp and affected service(s)\n- Confirm initial severity assessment\n\n#### Triage\n\n- Determine root cause hypothesis\n- Identify blast radius (affected services, users, regions)\n- Assign roles: Incident Commander (SEV1\u002FSEV2), Communication Lead, Technical Lead\n\n#### Mitigation\n\n- Apply immediate mitigation (rollback, feature flag, scaling, failover)\n- Verify mitigation effectiveness\n- Document mitigation steps taken\n\n#### Resolution\n\n- Implement permanent fix\n- Verify resolution across all affected components\n- Confirm service restoration to normal operation\n- Update status page with resolution notice\n\n### Step 4 — Communicate\n\nGenerate communication templates based on severity and channels. Frequency varies by severity level.\n\n#### Status Page Template\n\n```markdown\n**[INVESTIGATING\u002FIDENTIFIED\u002FMONITORING\u002FRESOLVED]** — {{PROJECT_NAME}}\n\n**Impact:** [Description of user-facing impact]\n**Affected Services:** [List of affected services]\n**Current Status:** [What we know and what we are doing]\n**Next Update:** [Time of next update based on severity]\n```\n\n#### Slack\u002FTeams Internal Update Template\n\n```markdown\n:rotating_light: **Incident Update — [SEV level]**\n**Service:** [affected service]\n**Impact:** [description]\n**Status:** [Investigating\u002FMitigating\u002FResolved]\n**IC:** [Incident Commander name]\n**Timeline:**\n- [HH:MM] [Event description]\n**Next Steps:** [what happens next]\n**Next Update:** [time]\n```\n\n#### Email Stakeholder Notification Template\n\n```markdown\nSubject: [SEV level] Incident — [Brief description]\n\nDear Stakeholders,\n\nWe are currently experiencing [description of the issue]\naffecting [scope of impact].\n\n**Severity:** [SEV1\u002FSEV2\u002FSEV3\u002FSEV4]\n**Impact:** [User-facing impact description]\n**Status:** [Current status]\n**ETA for Resolution:** [Estimate or \"Under investigation\"]\n\nWe will provide updates every [frequency based on severity].\n\nBest regards,\n[Team Name]\n```\n\n**Update Frequency by Severity:**\n\n| Severity | Update Frequency | Channels |\n|----------|-----------------|----------|\n| SEV1 | Every 30 min | Status Page, Slack, Email |\n| SEV2 | Every 1 hour | Status Page, Slack, Email |\n| SEV3 | Every 4 hours | Status Page, Slack |\n| SEV4 | Daily | Slack |\n\n### Step 5 — Postmortem\n\nIf `--postmortem` flag is provided, or severity is SEV1 or SEV2, generate a postmortem document from the `_TEMPLATE-POSTMORTEM.md` template.\n\n**Postmortem is triggered when:**\n\n- Severity is SEV1 (always)\n- Severity is SEV2 (always)\n- `--postmortem` flag is explicitly provided (any severity)\n\n**Postmortem document is pre-filled with:**\n\n- Incident timeline from the response flow\n- Severity classification and impact assessment\n- Mitigation and resolution steps taken\n- Participants and their roles\n- Action items identified during the response\n\nIf the postmortem template is not available, generate an inline postmortem with the basic structure:\n\n```markdown\n# Postmortem — [Incident Title]\n\n## Incident Summary\n| Field | Value |\n|-------|-------|\n| Severity | [SEV level] |\n| Date | [Date] |\n| Duration | [Duration] |\n| Affected Services | [Services] |\n\n## Timeline\n[Pre-filled from incident response]\n\n## Root Cause Analysis\n[To be completed]\n\n## Action Items\n[Pre-filled from tracked items]\n\n## Lessons Learned\n[To be completed]\n```\n\n### Step 6 — Track Action Items\n\nRegister all action items identified during the incident response. Each action item includes:\n\n| Field | Description |\n|-------|-------------|\n| ID | Sequential identifier (AI-001, AI-002, ...) |\n| Description | What needs to be done |\n| Owner | Person responsible |\n| Deadline | Target completion date |\n| Priority | HIGH \u002F MEDIUM \u002F LOW |\n| Status | OPEN \u002F IN_PROGRESS \u002F DONE |\n\n**Output format:**\n\n```markdown\n## Action Items\n\n| ID | Description | Owner | Deadline | Priority | Status |\n|----|-------------|-------|----------|----------|--------|\n| AI-001 | [description] | [owner] | [date] | HIGH | OPEN |\n| AI-002 | [description] | [owner] | [date] | MEDIUM | OPEN |\n```\n\n## Severity Definitions\n\n| Severity | Label | Description | Response Time | Update Frequency | Postmortem Required |\n|----------|-------|-------------|---------------|------------------|---------------------|\n| **SEV1** | Critical | Total service outage, significant financial loss, data breach | 15 min | 30 min | Yes (always) |\n| **SEV2** | High | Major feature unavailable, degraded experience for many users | 30 min | 1 hour | Yes (always) |\n| **SEV3** | Medium | Minor feature impacted, workaround available | 4 hours | 4 hours | Only if --postmortem |\n| **SEV4** | Low | Cosmetic issue, minimal impact | Next business day | Daily | Only if --postmortem |\n\n## Communication Templates\n\nSee Step 4 above for complete templates per channel (Status Page, Slack\u002FTeams, Email) and update frequency per severity level.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Severity not provided | Ask the user about the impact and suggest classification based on description |\n| Invalid severity (e.g., SEV5) | Reject with message: \"Invalid severity. Use SEV1, SEV2, SEV3, or SEV4\" |\n| `--postmortem` without template | Generate inline postmortem with basic structure |\n| No Incident Commander available | Assign the requesting user as IC and recommend finding a replacement |\n| Incomplete information | Proceed with available data, note gaps in postmortem |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-troubleshoot-operations | called-by | Escalates to this skill when an issue becomes a production incident |\n| sre-engineer (agent) | calls | Delegates reliability expertise and checklist validation via Agent tool |\n| sre-practices (KP) | reads | References `knowledge\u002Fsre-practices\u002F` for incident management processes |\n\n- Uses `_TEMPLATE-POSTMORTEM.md` for postmortem document generation. Fallback: inline postmortem with basic structure when template is absent.\n- Uses `_TEMPLATE-INCIDENT-RESPONSE.md` for severity classification reference\n- Can be used standalone or as part of on-call response workflow\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"context-budget":26,"user-invocable":27,"requires-capabilities":28},"Read, Write, Bash, Grep, Glob, Agent","[severity SEV1|SEV2|SEV3|SEV4] [--postmortem] [--notify]","medium",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-fintech-pci\u002F.claude\u002Fskills\u002Fx-handle-incident",1,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment","https:\u002F\u002Fgithub.com\u002Freview-bench","https:\u002F\u002Freview-bench.ai","An open benchmark for AI code review.","2026-10-27 06:56:37",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":27},[40,43,46],{"tool":41,"command":42},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-handle-incident",{"tool":44,"command":45},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-handle-incident",{"tool":47,"command":48},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-handle-incident","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-fintech-pci\u002F.claude\u002Fskills\u002Fx-handle-incident\u002FSKILL.md",[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",1768,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-fintech-pci\u002F.claude\u002Fskills\u002Fx-handle-incident\u002FREADME.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M757M8J48TQ1Y3X25GSJBXAS","x-parallel-eval","Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan \u002F x-story-plan, applies the parallelism-heuristics knowledge pack (hard \u002F regen \u002F soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fx-parallel-eval\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M757M57XMR9546S69466HDWT","parallelism-heuristics","Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard \u002F regen \u002F soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fparallelism-heuristics\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M757M11SZ8P1VCQABT08QVYA","x-watch-pr-ci","Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-watch-pr-ci\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M757KW53K8KFPGADFB4PH949","x-validate-docs","Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared\u002Fauto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-validate-docs\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M757KQZHSA10MKC0CR571D60","x-update-system-architecture","Incrementally updates docs\u002Farchitecture\u002Fsystem.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component\u002Fintegration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-system-architecture\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M757KKBT5Q1SVF8DMJBVF46M","x-update-architecture","Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-architecture\u002FSKILL.md",[],[]]