Forgent analyze-code-repository

Systematically analyze repository structure to locate code relevant to the issue-based skill consuming repository, issue_description to produce code_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/sweagent-v1/output-standard/skills/analyze-code-repository" ~/.claude/skills/mirandaguillaume-forgent-analyze-code-repository && rm -rf "$T"

manifest: internal/bench/fixtures/swebench-imported/sweagent-v1/output-standard/skills/analyze-code-repository/SKILL.md

source content

Analyze Code Repository

Guardrails

Timeout after 300 seconds of file analysis
Limit file reads to 100 files per analysis
Only analyze files with common programming extensions (.py, .js, .java, etc.)

Context

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

Strategy

Approach: Systematically analyze repository structure to locate code relevant to the issue Tools: read_file, grep, search

Steps

Find and read code files relevant to the problem description
Analyze the repository structure and dependencies
Document relevant code components and their relationships

Security

Filesystem: read-only
Network: none