mcpField
G
git:analyze-issue

git:analyze-issue

github.com/neolabhqDevelopment1.8k419 installsUpdated 10w ago
Repository

About git:analyze-issue

A skill that analyzes a GitHub issue and produces a saved technical specification. It examines issue details and related code, then documents the approach, implementation, tests, affected files, and success criteria.

Key features

  1. 01Load or fetch GitHub issue details
  2. 02Review requirements and related code
  3. 03Draft a structured technical specification
  4. 04Document implementation and test plans
  5. 05Save the specification under specs/issues

Use cases

  1. 01Turn a GitHub issue into an implementation plan
  2. 02Scope code changes and affected files
  3. 03Define tests and success criteria before development

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/neolabhq/context-engineering-kit --skill git:analyze-issue

After installing, type/git:analyze-issuein Claude Code to confirm it loaded.

Details

From the project README

Please analyze GitHub issue #$ARGUMENTS and create a technical specification.

Follow these steps:

  1. Check if the issue is already loaded:

    • Look for the issue file in ./specs/issues/ folder
    • File naming pattern: <number-padded-to-3-digits>-<kebab-case-title>.md
    • If not found, fetch the issue details from GitHub (see step 2)

  2. Fetch the issue details (if not already loaded):

    • Read .claude/commands/load-issues.md to understand how to fetch issue details
    • Save the issue file following the load-issues.md format

  3. Understand the requirements thoroughly

  4. Review related code and project structure

  5. Create a technical specification with the format below

Technical Specification for Issue #$ARGUMENTS

Issue Summary

  • Title: [Issue title from GitHub]
  • Description: [Brief description from issue]
  • Labels: [Labels from issue]
  • Priority: [High/Medium/Low based on issue content]

Problem Statement

[1-2 paragraphs explaining the problem]

Technical Approach

[Detailed technical approach]

Implementation Plan

  1. [Step 1]
  2. [Step 2]
  3. [Step 3]

Test Plan

  1. Unit Tests:
    • [test scenario]
  2. Component Tests:
    • [test scenario]
  3. Integration Tests:
    • [test scenario]

Files to Modify

Files to Create

Existing Utilities to Leverage

Success Criteria

  • [criterion 1]
  • [criterion 2]

Out of Scope

  • [item 1]
  • [item 2]

Remember to follow our strict TDD principles, KISS approach, and 300-line file limit.

IMPORTANT: After completing your analysis, SAVE the full technical specification to: ./specs/issues/<number-padded-to-3-digits>-<kebab-case-title>.specs.md

For example, for issue #7 with title "Make code review trigger on any *.SQL and .sh file changes", save to: ./specs/issues/007-make-code-review-trigger-on-sql-sh-changes.specs.md

After saving, provide a brief summary to the user confirming:

  • Issue number and title analyzed
  • File path where the specification was saved
  • Key highlights from the specification (2-3 bullet points)

Comments

Markdown supported