SkillsAdd

neolabhq/context-engineering-kit

analyze-issue

Analyze a GitHub issue and create a detailed technical specification

All-time #9539 Trending #9734 First seen Apr 23, 2026
8-week activity · all time api

Installation

$ npx skills add neolabhq/context-engineering-kit --skill analyze-issue
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

terraform-azurerm-set-diff-analyzer Similar name
github/awesome-copilot

Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive d…

8.9K installs
analyze Similar name
anthropics/knowledge-work-plugins

Answer data questions -- from quick lookups to full analyses. Use when looking up a single metr…

5.3K installs
tao-analyze-changenet-rca Similar name
nvidia/skills

Performs deep Root Cause Analysis (RCA) on NVIDIA TAO Visual ChangeNet classification experimen…

1.6K installs
tao-analyze-gaps-visual-changenet Similar name
nvidia/skills

Performs gap analysis on NVIDIA TAO VCN Classify (Visual Component Net) experiments by invoking…

1.5K installs
tao-analyze-gaps-vlm-bcq Similar name
nvidia/skills

Extract false-positive and false-negative gaps from VLM binary-classification-question (BCQ, ye…

1.5K installs
margin-analyzer Similar name
anthropics/knowledge-work-plugins

Analyzes unit economics by product or service using PayPal merchant insights and QuickBooks cos…

1.4K installs

Also in this package

Other skills from neolabhq/context-engineering-kit · top by installs.

npx skills add neolabhq/context-engineering-kit
prompt-engineering 1.3K context-engineering 1.2K thought-based-reasoning 1.2K update-docs 1.1K multi-agent-patterns 1.1K brainstorm 1.2K write-concisely 1.2K reflect 1.2K critique 1.1K subagent-driven-development 1.1K

Browse all from neolabhq/context-engineering-kit

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 1.7K
License LICENSE
Default branch master
Open issues 6
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,229 B
  • docs SUMMARY.md 89 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,100 installs

SKILL.md

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)

  1. 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

  1. Understand the requirements thoroughly
  2. Review related code and project structure
  3. 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]

  1. Component Tests:

- [test scenario]

  1. Integration Tests:

- [test scenario]

Files to Modify

  • [file path]: [changes]

Files to Create

  • [file path]: [purpose]

Existing Utilities to Leverage

  • [utility name/path]: [purpose]

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)