Analyze incident logs and reports to identify root causes and quantify tech debt.
npx skills add https://github.com/blakeox/llm-skills --skill investigator-blakeox
Please help me install this Agent Skill. Skill: investigator Source: https://github.com/blakeox/llm-skills/tree/main/openclaw/skills/investigator Command: npx skills add https://github.com/blakeox/llm-skills --skill investigator-blakeox
This Skill helps teams by providing tools to analyze failures, project trends, and quantify tech debt, enabling better understanding and management of systemic issues.
Use the investigator skill to analyze the latest postmortem document in your project repository.
High-intent search queries and answers about installing and using this skill.
Root cause analysis processes event evidence like logs and postmortem reports to reconstruct incident timelines and identify underlying causes. It evaluates version history and incident documentation to pinpoint systemic failures for software teams.
Quantifying technical debt involves evaluating version history and project reports to assess long-term costs and risks. This analysis helps software teams prioritize tech debt tasks based on their systemic impact and accumulated maintenance burden.
Detecting team output trends requires reviewing logs and reports over time to identify recurring patterns. This Skill processes historical evidence from retrospectives to highlight areas for improvement and long-term technical planning.
Yes, you can analyze postmortem documents directly to extract incident timelines and root causes. The Skill processes evidence from project reports and version history to facilitate investigations without requiring external dependencies.
Incident trend analysis works by processing existing logs, reports, and version history evidence directly. It requires no external dependencies or monitoring tool integrations to detect patterns and quantify technical debt during retrospectives.
yusufcmgGenerates blameless postmortem documents with root cause analysis, timelines, and action items for incident reviews.
MichaelSolatiScan codebases for technical debt indicators and prioritize findings.
redhat-etInvestigate platform incidents by gathering evidence and generating root cause documentation.
Harshal1841ADetect, analyze, and track technical debt across codebases.
