incident
Skill82 starsChanged 2 days agoLicence not identifiedView on GitHub
引導事故回應、根因分析與事後檢討文件撰寫。 Use when: 正式環境事故、服務中斷回應、撰寫事後檢討、根因分析（RCA）。 Not for: 在故障發生前設計重試與檢查點——請用 /durable；設定告警門檻與 Error Budget 政策——請用 /slo。 Keywords: incident, outage, post-mortem, RCA, root cause, 事故, 服務中斷, 事後檢討, 根因分析.
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- DataWithBaraa/claude-code-data-engineering-skills★ 52same name
- manusco/resonance★ 38same name
- ulises-jeremias/agent-toolkit★ 19same name
- lalulali/vespyr★ 11same name
- greglas75/zuvo★ 8same name
- NotHarshhaa/devops-skills★ 8same name
- chancegraff/rules-for-claude★ 4same name
- gonimar/claude-web-studio★ 4same name
- umararshad4/honey-stack★ 4same name
- gufranco/claude-engineering-rules★ 3same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use handover, retro and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
anujdutt9Skillhandover
Also in 3 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 5 projects that use this
Microsoft AzureSkilltest
Also in 4 projects that use this
- Microsoft AzureSkill
design
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 4 projects that use this
In this repository173 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- skills/tools/copilot/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- commitSkill
- comprehendSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- open-workSkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- spec-deriveSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill
- ac-coverageSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.