issue-analyzing

To analyze a GitHub issue with code context, provide the issue number and optional repository context. The skill fetches issue metadata and comments from GitHub, then uses the chunkhound-integration MCP tool to research the affected code areas and produce a structured analysis.

Triage GitHub issues across multiple repositories by providing the specific issue number and repo context. The skill extracts scope, affected areas, and resolution status, optionally using triage context to guide the code research for a structured multi-section analysis output.

Yes, the chunkhound-integration MCP plugin is required to analyze issue scope. The skill depends on this companion plugin to perform semantic code research that identifies affected code areas based on the GitHub issue description and comments.

Yes, you can check the resolution status of an existing GitHub issue. The skill fetches authoritative issue data and comments from GitHub, combines it with code-context research, and returns a structured output detailing the problem scope, affected areas, and current resolution status.

Combining GitHub issue data with semantic code research improves triage by linking issue descriptions to actual affected code areas. The chunkhound-integration MCP uses an incremental research strategy to map issue scope to code, producing a structured analysis with accurate resolution status.

Analyzing GitHub issues without repo context limits the ability to identify affected code areas accurately. While the skill fetches metadata and comments from GitHub, providing optional repo context and triage context helps guide the chunkhound code research for more precise structured analysis.