ghs-issue-analyze

Analyze GitHub issues by inspecting the codebase and posting structured analysis comments.

2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Atypical-Consulting/GitHubSkills --skill ghs-issue-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghs-issue-analyze
Source: https://github.com/Atypical-Consulting/GitHubSkills/tree/main/.claude/skills/ghs-issue-analyze
Command: npx skills add https://github.com/Atypical-Consulting/GitHubSkills --skill ghs-issue-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the in-depth analysis of GitHub issues by inspecting the codebase, providing crucial insights into feasibility, complexity, affected files, and suggested approaches, thereby accelerating the implementation process.

Core Features & Use Cases

  • Codebase Inspection: Automatically clones the repository and searches the codebase for relevant files and patterns related to the issue.
  • Complexity Assessment: Evaluates the issue's complexity based on criteria like files changed, cross-module impact, test changes, and external dependencies.
  • Structured Analysis: Generates a detailed analysis report including feasibility, effort estimation, affected areas, suggested approach, and potential risks.
  • Use Case: When a new bug report comes in, use this Skill to get a clear understanding of what code needs to be changed, how difficult it will be, and the estimated effort before starting any work.

Quick Start

Use the ghs-issue-analyze skill to analyze issue number 42.

Frequently Asked Questions about ghs-issue-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze GitHub issue complexity and identify affected files automatically?

To analyze GitHub issue complexity, this Skill inspects the codebase and posts a structured comment evaluating feasibility, cross-module impact, affected files, and estimated effort. It clones the repository to search for relevant patterns related to the issue.

What is the best way to assess bug feasibility before starting implementation?

Assessing bug feasibility requires evaluating the codebase impact and potential risks. This Skill generates a detailed analysis report suggesting an implementation approach and estimating effort based on files changed and external dependencies.

How do I get a structured implementation approach for a new GitHub issue?

You can get a structured implementation approach by running this Skill against a specific issue number. It evaluates the issue context, inspects the codebase, and posts a comment outlining the suggested approach, affected areas, and potential risks.

Do I need the gh CLI to inspect repositories and assess issue complexity?

Yes, you need the gh CLI installed for GitHub API interactions and git for repository operations. These tools allow the Skill to clone repositories, search code patterns, and post structured analysis comments directly to the issue.

Can I evaluate cross-module impact and test changes for a bug report automatically?

Yes, you can evaluate cross-module impact and test changes automatically. The Skill assesses issue complexity by inspecting repository files, evaluating external dependencies, and generating a report detailing affected areas and potential risks.

What are the limitations of automating codebase inspection for issue analysis?

Automating codebase inspection depends on having local git and gh CLI access for repository operations. While it identifies affected files and estimates effort, the analysis is limited to the codebase patterns found during the automated clone and search process.