Forgent bug-localization

Analyze GitHub issues to localize bugs by identifying affected components-based skill consuming github_issue, codebase_files to produce bug_location_analysis

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/agentless-repair/output-standard/skills/bug-localization" ~/.claude/skills/mirandaguillaume-forgent-bug-localization && rm -rf "$T"

manifest: internal/bench/fixtures/swebench-imported/agentless-repair/output-standard/skills/bug-localization/SKILL.md

source content

Bug Localization

Guardrails

Focus only on identifying the bug location and root cause
Do not make any code changes during analysis
timeout: 300

Context

Consumes: github_issue, codebase_files Produces: bug_location_analysis Memory: short-term

Strategy

Approach: Analyze GitHub issues to localize bugs by identifying affected components Tools: read_file, grep, search

Steps

Read and parse the GitHub issue description to identify affected components
Search codebase to locate relevant files and functions/classes
Narrow down to the specific code paths involved in the reported behavior

Security

Filesystem: read-only
Network: none