New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Analyze Issue

by NeoLabHQ in NeoLabHQ/context-engineering-kit

Analyze a GitHub issue and create a detailed technical specification

GPL-3.0Auto-check passedTesting & QA

Install Analyze Issue

skills CLI
$ npx skills add NeoLabHQ/context-engineering-kit --skill analyze-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NeoLabHQ/context-engineering-kit analyze-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analyze-issue .claude/skills/analyze-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analyze-issue
GitHub stars
1.8k
Token cost
~558 tokens
SKILL.md length
267 words
Files
1
Skills in repo
57
Repo updated
First seen
Licence
GPL-3.0

At a glance

Analyze a GitHub issue and create a detailed technical specification

  • Works in 5 steps: Check if the issue is already loaded → Fetch the issue details (if not already… → Understand the requirements thoroughly → …
  • Testing & QA work in your project
  • SKILL.md covers Issue Summary, Problem Statement, Technical Approach and Implementation Plan, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Analyze Issue is an agent skill from NeoLabHQ/context-engineering-kit. Analyze a GitHub issue and create a detailed technical specification

Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. It works with GitHub. The repository describes itself as: Hand-crafted Claude Code Skills focused on improving agent results quality. Compatible with OpenCode, Cursor, Antigravity, Gemini CLI, and others. Includes CodeRabbit open-source… The licence is GPL-3.0.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/analyze-issue”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Check if the issue is already loaded
  2. Fetch the issue details (if not already loaded)
  3. Understand the requirements thoroughly
  4. Review related code and project structure
  5. Create a technical specification with the format below

What it can do on your machine

Read from SKILL.md and the folder at commit 23e2428. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Analyze Issue loads about 558 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 267 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~558

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NeoLabHQ/context-engineering-kit at commit 23e2428, republished under its GPL-3.0 licence (© NeoLabHQ). 267 words, ~558 tokens.

Download SKILL.mdSave it as .claude/skills/analyze-issue/SKILL.md (or your agent's skills folder).
name
analyze-issue
description
Analyze a GitHub issue and create a detailed technical specification

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)

© NeoLabHQ, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/analyze-issue of NeoLabHQ/context-engineering-kit.

Open the folder on GitHubat commit 23e2428

Compare with similar skills

Analyze Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Analyze Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyze Issue this skillNeoLabHQ/context-engineering-kit1.8k—~558Automated safety check: PassGPL-3.0
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness1.7k—~1.6kAutomated safety check: PassMIT
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Triage CI Flakepayloadcms/payload45k—~4.4kAutomated safety check: PassMIT
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb6.7k—~4.4kAutomated safety check: PassApache-2.0
Create GitHub IssueNVIDIA/OpenShell16k—~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Weavebench Cua Reproduce

    AMAP-ML/LongHorizon-Harness

    Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.

    1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Triage CI Flake

    payloadcms/payload

    A skill your agent uses when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests

    45k GitHub stars~4.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • GreptimeDB Fuzz CI Failure Investigation

    GreptimeTeam/greptimedb

    Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.

    6.7k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    16k GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Cherry Studio Regression Tests

    CherryHQ/cherry-studio

    Runs Cherry Studio's critical-path regression suite as deterministic Playwright E2E tests through a GitHub workflow on macOS and Windows runners.

    53k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

More from NeoLabHQ/context-engineering-kit

All 57 skills in this repo

  • Git Notes

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides…

    1.8k GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Load PR Comments

    NeoLabHQ/context-engineering-kit

    A skill your agent uses to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/.md for parallel agents to fix.

    1.8k GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Prompt Engineering

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing…

    1.8k GitHub stars~4.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Multi Agent Patterns

    NeoLabHQ/context-engineering-kit

    Design multi-agent architectures for complex tasks. An agent skill from NeoLabHQ/context-engineering-kit.

    1.8k GitHub starsUsed in 6 repos~6k tokens
    Auto-check passed

  • Review PR

    NeoLabHQ/context-engineering-kit

    Review an existing GitHub pull request and post inline review comments on its diff.

    1.8k GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Subagent Driven Development

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or…

    1.8k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Analyze Issue

What does Analyze Issue do?

Analyze a GitHub issue and create a detailed technical specification. Analyze Issue is an agent skill from NeoLabHQ/context-engineering-kit.

When should I use Analyze Issue?

Analyze Issue fits situations like: testing & QA work in your project.

How do I install Analyze Issue in Claude Code?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill analyze-issue -a claude-code`. Or copy the skill folder (skills/analyze-issue in NeoLabHQ/context-engineering-kit) into .claude/skills/analyze-issue in your project. Claude Code loads it when a task matches its description.

How do I install Analyze Issue in Codex?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill analyze-issue -a codex`. Or copy the skill folder (skills/analyze-issue in NeoLabHQ/context-engineering-kit) into .agents/skills/analyze-issue in your project. Codex loads it when a task matches its description.

Can I use Analyze Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NeoLabHQ/context-engineering-kit --skill analyze-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-issue, .gemini/skills/analyze-issue, .github/skills/analyze-issue and .opencode/skills/analyze-issue in your project.

What does Analyze Issue need to run?

SKILL.md names no scripts, command-line tools or credentials: Analyze Issue is instructions for the agent only.

Does Analyze Issue access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Analyze Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Analyze Issue use?

Analyze Issue is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analyze Issue use?

About 558 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Analyze Issue?

Skills that share tags, products or a category with Analyze Issue: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Triage CI Flake (payloadcms/payload, 45k stars) and GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyze Issue?

NeoLabHQ (a GitHub organization) maintains it in NeoLabHQ/context-engineering-kit, which has 1,750 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 26, 2026.

Source: NeoLabHQ/context-engineering-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.