Create a structured review after a production incident, focusing on systems and processes without blaming individuals. Reconstruct events, quantify impact, investigate causes, and document specific follow-up actions with named owners and deadlines.
中文简介正在准备中。当前显示英语简介。
- Write a review after a production outage
- Reconstruct an incident timeline from records
- Separate root causes from contributing factors
github/awesome-copilot☆ 4万2026年10月20日 更新
Investigates GitHub or Linear issues through code, change history, and reproduction attempts. Produces a structured handoff covering causes, assumptions, effort, and impact, then requests the appropriate Factory workflow stage update when applicable.
中文简介正在准备中。当前显示英语简介。
- Investigating the root cause of a reported bug
- Checking for duplicate issues or regressions
- Preparing findings for whoever plans the fix
mastra-ai/mastra☆ 2.9万2026年10月19日 更新
Analyze a difficult problem with two agents chosen for contrasting reasoning styles. They independently investigate causes and plan a solution, then exchange arguments to resolve disagreements and produce a shared recommendation without changing files.
中文简介正在准备中。当前显示英语简介。
- Investigating the root cause of a persistent problem
- Reconsidering an approach after repeated failed attempts
- Comparing perspectives on a difficult planning problem
getpaseo/paseo☆ 2.1万2026年10月19日 更新
Investigate failing or slow BigQuery jobs and unexpected cost increases. Compare execution details and resource usage with a normal baseline to isolate bottlenecks, identify likely causes, and determine practical remediation steps.
中文简介正在准备中。当前显示英语简介。
- Investigate failed or slow BigQuery jobs
- Locate bottlenecks in execution stages
- Diagnose sudden increases in query or capacity costs
google/skills☆ 2.1万2026年10月20日 更新
Investigate recurring problems by mapping feedback loops, the cycles through which effects influence their causes. Identify underlying structures, match known patterns, and assess where changes could help and what unintended effects they might produce.
中文简介正在准备中。当前显示英语简介。
- Investigating recurring incidents
- Understanding coordination problems as teams grow
- Assessing unintended effects before changing a policy
danielmiessler/LifeOS☆ 2万2026年9月4日 更新
Investigate errors, crashes, and unexpected behavior by reproducing failures, tracing execution, and comparing logs. Tests one explanation at a time, then provides a verified fix, supporting evidence, and tests or safeguards to prevent recurrence.
中文简介正在准备中。当前显示英语简介。
- Investigate error messages and execution traces
- Find the cause of an application crash
- Compare logs to locate a failure
Jeffallan/claude-skills☆ 1.2万2026年10月17日 更新
Investigate production incidents and bugs using logs, metrics, and code evidence. The skill guides hypothesis testing, root cause analysis, fix validation, and reusable investigation notes, with access to configured observability tools such as Axiom.
中文简介正在准备中。当前显示英语简介。
- Investigate production outages and rising error rates
- Trace causes using logs, metrics, and code
- Reproduce bugs and validate minimal fixes
openclaw/clawhub☆ 95232026年10月19日 更新
Build an MCP integration skill using a template that reads server-specific reference notes before calling tools. The Sentry example gathers unresolved errors, groups them by likely root cause, and produces a report with investigation suggestions.
中文简介正在准备中。当前显示英语简介。
- Design a skill that integrates with an MCP server
- Document server-specific query pitfalls
- Group Sentry errors by likely root cause
FlorianBruniaux/claude-code-ultimate-guide☆ 62062026年10月20日 更新
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
中文简介正在准备中。当前显示原文说明。
wesammustafa/Claude-Code-Everything-You-Need-to-Know☆ 34532026年10月20日 更新
Locate root causes of failing regression tests by analyzing code changes, error messages, and test dependencies. Use when regression tests start failing after code changes, investigating test failures in CI/CD, debugging flaky tests, or understanding why previously passing tests now fail. Analyzes git diffs, stack traces, test output, and dependency changes to produce structured markdown reports ranking likely causes. Triggers when users ask to find why tests are failing, debug regression failures, investigate test breakage, or analyze failing test suites.
中文简介正在准备中。当前显示原文说明。
ArabelaTso/Skills-4-SE☆ 2562026年8月21日 更新
Finds the cause of a hard bug by running several read-only subagents in parallel, each attacking it from a different angle (change history, code path, data and state, environment, reproduction), then checking their evidence, ranking the hypotheses and naming the one experiment that would confirm the leader. It diagnoses and does not fix. Use when someone says "hunt this bug with multiple agents", "swarm on this regression", "investigate in parallel", "find the root cause", or when a failure is intermittent, crosses components, or has resisted a first look.
中文简介正在准备中。当前显示原文说明。
TerminalSkills/skills☆ 1722026年10月14日 更新
Investigate the root cause of a recurring or systemic defect across a series of incidents, not a single one. Use on the third recurrence, or when someone asks 'why again?', 'five whys', 'fix the root'. Skip for one or two ordinary cases, an already proven simple cause, or a one-off external outage. Triggers: /five-whys, five whys, fix the root.
中文简介正在准备中。当前显示原文说明。
tonydzi/second-brain-starter-kit☆ 92026年10月20日 更新
Turn Strix vulnerability findings into focused code fixes, prioritized by severity. Address root causes, rerun security scans and original exploit examples, and report the changes and verification results for each issue.
中文简介正在准备中。当前显示英语简介。
- Fixing vulnerabilities reported by Strix
- Prioritizing remediation by severity
- Retesting original exploits after code changes
usestrix/strix☆ 7万2026年10月20日 更新
Investigate bugs and slow applications through reproducible examples, logs, environment comparisons, and hypothesis testing. The skill structures root cause analysis and performance measurement, helping developers narrow down failures and verify that a fix works.
中文简介正在准备中。当前显示英语简介。
- Investigate bugs that occur only occasionally
- Measure and locate performance bottlenecks
- Collect evidence and reproduce production failures
wshobson/agents☆ 4.1万2026年10月20日 更新
Investigate a mismatch between the general ledger and a supporting ledger by tracing both sides to their original entries. Compare transaction details and return a concise cause, responsible team, expected resolution date, and recommended action.
中文简介正在准备中。当前显示英语简介。
- Investigating a classified ledger reconciliation mismatch
- Comparing posting dates and exchange rates on both sides
- Identifying account mapping errors or duplicate transactions
anthropics/financial-services☆ 4万2026年9月22日 更新
Investigate failed Power Automate cloud flows through FlowStudio MCP. Inspect each action’s inputs and outputs, trace incorrect data upstream, fix expression or data issues, and replay a previous run to check the repair.
中文简介正在准备中。当前显示英语简介。
- Investigate why a cloud flow failed
- Find null values or incorrect field paths in expressions
- Inspect HTTP error response details
github/awesome-copilot☆ 4万2026年10月20日 更新
Turn defects found during Oracle-to-PostgreSQL migration into structured bug reports. Document expected and actual behavior, reproduction steps, severity, root causes, proposed changes, and validation on both databases so teams can act on the findings.
中文简介正在准备中。当前显示英语简介。
- Documenting behavioral differences found during migration
- Organizing reproduction steps and test data
- Recording fixes, affected files, and validation steps
github/awesome-copilot☆ 4万2026年10月20日 更新
Guide a structured review after a security incident, using timelines and response data to identify root causes and process gaps. Produce review notes, response metrics, and practical improvements with named owners and deadlines.
中文简介正在准备中。当前显示英语简介。
- Reviewing response after a ransomware incident
- Turning exercise findings into process improvements
- Updating incident response playbooks
mukul975/Anthropic-Cybersecurity-Skills☆ 3.5万2026年8月31日 更新
Fix defects in Composio SDK through focused reproduction, root-cause analysis, regression tests that check for recurrence, and targeted verification. Use it for reported bugs, failing tests, CI regressions, runtime errors, or incorrect SDK behavior.
中文简介正在准备中。当前显示英语简介。
- Reproducing and fixing reported SDK bugs
- Investigating failing tests
- Fixing regressions in automated CI checks
ComposioHQ/composio☆ 3.1万2026年10月20日 更新
Investigate a GitHub issue or bug report by tracing code, checking relevant history, and testing the diagnosis where needed. Receive a concise verdict, supporting evidence, a proposed fix direction, and a record for follow-up questions.
中文简介正在准备中。当前显示英语简介。
- Triaging a newly reported bug
- Tracing the root cause of unexpected behavior
- Investigating a regression and its originating change
mastra-ai/mastra☆ 2.9万2026年10月19日 更新
Repair an entire broken feature by mapping its files and dependencies, checking configuration and logs, and confirming root causes. Apply fixes in sequence, then test the feature and the code that uses it.
中文简介正在准备中。当前显示英语简介。
- Repairing a broken feature from start to finish
- Investigating imports and configuration together
- Finding root causes across multiple modules
alirezarezvani/claude-skills☆ 2.8万2026年8月30日 更新
Assess Web3 vulnerability findings before submission by checking scope, reproducibility, prerequisites, and attack costs. Organize the root cause, measurable impact, working proof of concept, and proposed fix into an Immunefi report, with examples for comparison.
中文简介正在准备中。当前显示英语简介。
- Checking whether a finding is ready for submission
- Drafting an Immunefi vulnerability report
- Reviewing reproduction code and measurable impact
tradecatlabs/vibe-coding-cn☆ 1.8万2026年10月19日 更新
Investigate a bug's root cause, implement a focused repair, and verify the same behavior before and after the change. Select lasting regression tests, preserve reproduction evidence, and record the corrected user journey when possible.
中文简介正在准备中。当前显示英语简介。
- Investigating and fixing a bug without an existing candidate PR
- Proving a repair with failing-then-passing tests
- Consolidating regression checks into existing tests
omnigent-ai/omnigent☆ 1.1万2026年10月19日 更新
Investigate a reported bug before choosing a fix. Trace the actual failure, test competing explanations, and examine design history so the proposed change preserves intended behavior and clearly separates verified findings from unresolved assumptions.
中文简介正在准备中。当前显示英语简介。
- Reconstructing the conditions of a reported bug
- Distinguishing a symptom from its underlying cause
- Checking intended behavior in tests and history
omnigent-ai/omnigent☆ 1.1万2026年10月19日 更新