git:analyze-issue

Analyze a GitHub issue and generate a structured technical specification.

Updated Mar 4, 2026

Search Tags:#automation #git #planning #github #requirements #technical-specification #issue-analysis

Ready to run

npx skills add https://github.com/dalawwa/labor-methods --skill git-analyze-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git:analyze-issue
Source: https://github.com/dalawwa/labor-methods/tree/main/.cek/plugins/git/skills/analyze-issue
Command: npx skills add https://github.com/dalawwa/labor-methods --skill git-analyze-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issues often contain insufficient or ambiguous requirements. This Skill analyzes an issue and converts it into a detailed, actionable technical specification that can guide design and implementation.

Core Features & Use Cases

Analyze an issue by number to extract title, description, labels, and priority.
Retrieve issue details from GitHub or from local load if already saved.
Generate a structured technical specification with sections such as Issue Summary, Problem Statement, Technical Approach, Implementation Plan, Test Plan, and Files to Modify/Create.
Save the specification to the designated path under ./specs/issues with a <number>-<kebab-title>.specs.md filename.
Reference available utilities and ensure alignment with TDD principles.

Quick Start

Analyze a GitHub issue by number and generate a complete technical specification.

Frequently Asked Questions about git:analyze-issue

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

FAQPage Schema

How do I convert a GitHub issue into a technical specification?▼

You can turn GitHub issues into technical specifications by fetching issue details and generating a structured spec document with sections like Issue Summary, Technical Approach, and Test Plan, then saving it to your local specs directory.

What is the best way to create an implementation plan from ambiguous GitHub requirements?▼

Generating an implementation plan from ambiguous GitHub requirements involves analyzing the issue's title, description, and labels to produce a detailed technical specification that aligns with TDD principles and outlines specific files to modify.

Can I generate a test plan directly from a GitHub issue?▼

Yes, you can generate a test plan directly from a GitHub issue by analyzing the issue details and producing a structured technical specification document that includes a dedicated Test Plan section alongside the Implementation Plan.

How does issue analysis handle GitHub caching for local specs?▼

Issue analysis handles GitHub caching by retrieving issue details from GitHub or using local caches when available, ensuring the technical specification generation uses the local specs path if the issue is already loaded.

Does this technical specification generator require any external dependencies?▼

No, this technical specification generator operates without external dependencies, directly analyzing GitHub issues and saving the resulting structured markdown specification file to a designated local directory.