git-analyze-issue

Analyze GitHub issues to generate structured technical specification documents.

Updated Mar 10, 2026

Search Tags:#automation #documentation #github #issue tracking #development planning #technical specification

Ready to run

npx skills add https://github.com/Gamezar/opencode-cek --skill git-analyze-issue-gamezar

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed technical specifications directly from GitHub issues, streamlining the development planning process.

Core Features & Use Cases

Issue Analysis: Fetches and analyzes GitHub issue details.
Specification Generation: Creates a structured technical specification document.
Use Case: When a new feature request is logged as a GitHub issue, this Skill can automatically generate a comprehensive technical specification, including problem statement, approach, implementation plan, and test plan, ready for review.

Quick Start

Analyze GitHub issue number 123 and create a 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 generate technical specifications from GitHub issues?▼

To generate technical specifications from GitHub issues, the system fetches and analyzes issue data, then formats it according to a predefined template. This converts issue details into structured technical documents for development planning.

Can I automate development planning from GitHub issue tracking?▼

Automating development planning from GitHub issue tracking is achievable by analyzing issue details. This workflow automatically creates comprehensive technical specifications, including the implementation approach and test plan, ready for team review.

What is the best way to turn a GitHub feature request into a technical spec?▼

Turning a GitHub feature request into a technical spec is best handled by an automated issue analysis workflow. It extracts the problem statement and implementation plan directly from the issue to ensure structured technical documentation.

Do I need to manually format issue details for project planning workflows?▼

Manually formatting issue details for project planning workflows is unnecessary. The automation fetches GitHub issue data and applies a predefined specification template, structuring the technical details automatically for your development planning.

What limitations exist when generating technical specs from GitHub issues?▼

A limitation when generating technical specs from GitHub issues is the reliance on a predefined specification template. The output structure is fixed to the template's sections, meaning highly unconventional issue formats may not convert perfectly without manual adjustments.