Forgent identify-root-cause

Identify the root cause of the issue through detailed code examination-based skill consuming code_analysis, issue_description to produce root_cause

install

source · Clone the upstream repo

git clone https://github.com/mirandaguillaume/forgent

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/mirandaguillaume/forgent "$T" && mkdir -p ~/.claude/skills && cp -r "$T/internal/bench/fixtures/swebench-imported/sweagent-v1/output-standard/skills/identify-root-cause" ~/.claude/skills/mirandaguillaume-forgent-identify-root-cause && rm -rf "$T"

manifest: internal/bench/fixtures/swebench-imported/sweagent-v1/output-standard/skills/identify-root-cause/SKILL.md

source content

Identify Root Cause

Guardrails

Timeout after 180 seconds of root cause analysis
Focus analysis on the most relevant code sections

Context

Consumes: code_analysis, issue_description Produces: root_cause Memory: short-term

Strategy

Approach: Identify the root cause of the issue through detailed code examination Tools: read_file, grep

Steps

Examine the analyzed code components for potential issues
Trace through the logic to identify the source of the problem
Determine the specific cause that needs to be addressed

Security

Filesystem: read-only
Network: none