Forgent github-issue-analyzer

Analyze GitHub issues to understand bugs in Python code-based skill consuming github_issue, python_codebase to produce issue_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/aider-editblock/output-standard/skills/github-issue-analyzer" ~/.claude/skills/mirandaguillaume-forgent-github-issue-analyzer && rm -rf "$T"

manifest: internal/bench/fixtures/swebench-imported/aider-editblock/output-standard/skills/github-issue-analyzer/SKILL.md

source content

Github Issue Analyzer

Guardrails

Focus only on understanding the problem, not implementing fixes
Only analyze standard Python code
Maximum 15 minutes per issue analysis

Context

Consumes: github_issue, python_codebase Produces: issue_analysis Memory: short-term

Strategy

Approach: Analyze GitHub issues to understand bugs in Python code Tools: read_file, grep, search

Steps

Read and understand the GitHub issue to identify the bug
Analyze relevant code files to understand current behavior
Determine what changes are needed to fix the issue

Security

Filesystem: read-only
Network: none