git:analyze-issue

Analyze GitHub issues and generate technical specifications with test plans.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/luicabref97/sushi-jungle-web --skill git-analyze-issue-luicabref97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git:analyze-issue
Source: https://github.com/luicabref97/sushi-jungle-web/tree/main/.agents/skills/git-analyze-issue
Command: npx skills add https://github.com/luicabref97/sushi-jungle-web --skill git-analyze-issue-luicabref97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the conversion of GitHub issue descriptions into structured technical specifications, removing ambiguity for implementers and speeding up planning and development handoffs.

Core Features & Use Cases

  • Issue analysis and spec generation: Read or fetch a GitHub issue, synthesize its requirements, and produce a detailed technical specification including problem statement, approach, implementation steps, test plans, and success criteria.
  • Repository-aware workflow: Checks for existing locally cached issue files, fetches missing issues via the GitHub CLI following project conventions, and enforces naming and storage patterns.
  • Use Case: When a new feature request or bug report is filed, use this Skill to create a TDD-aligned implementation plan that developers can act on immediately.

Quick Start

Analyze GitHub issue #42 and generate a full technical specification saved to specs/issues using zero-padded numbering and kebab-case title.

Frequently Asked Questions about git:analyze-issue

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

FAQPage Schema
How do I turn GitHub issues into technical specifications?

Turn GitHub issues into technical specifications by fetching issue content via the GitHub CLI and synthesizing requirements into problem statements, implementation steps, test plans, and success criteria saved under specs/issues.

Can I generate a TDD-aligned implementation plan directly from a GitHub issue?

Generate a TDD-aligned implementation plan from a GitHub issue by analyzing its description and producing a detailed technical specification that includes test plans, implementation steps, and success criteria.

Does generating technical specs from GitHub issues require the GitHub CLI?

Generating technical specs from GitHub issues requires the GitHub CLI to fetch missing issue details when a locally cached issue file is not detected, ensuring repository-aware workflow compliance.

What is the best way to automate technical spec creation for GitHub feature requests?

Automate technical spec creation for GitHub feature requests by applying this Skill to analyze issue descriptions and output zero-padded, kebab-case files under specs/issues with structured implementation and test plans.

How does this approach handle repository structure and file naming conventions?

This approach handles repository structure by reviewing existing project conventions, detecting cached issue files, and enforcing strict storage patterns using zero-padded numbers and kebab-case filenames under specs/issues.

What file constraints apply when creating technical specifications from issues?

Technical specifications created from issues must adhere to TDD, KISS, and 300-line file constraints to ensure implementation plans remain simple, testable, and maintainable for developers.