Skip to main content
affpapa.org
RU EN
skill CX Codex

analyze-issue — Claude Code skill: what it does, how to install

Analyzes a GitHub issue, reviews related code, and saves a technical specification. Use it before starting work on a tracked task.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add NeoLabHQ/context-engineering-kit --skill analyze-issue -a claude-code
Open on GitHub

What analyze-issue does

The skill checks ./specs/issues/ for an existing issue record. If it cannot find one, it retrieves the issue details from GitHub, then examines the requirements, relevant code, and project structure.

Its specification covers the issue summary, problem statement, technical approach, implementation plan, and test plan. It also records files to change or create, existing utilities, success criteria, and out-of-scope work. The workflow follows TDD, KISS, and a 300-line file limit.

The result is saved under ./specs/issues/ with a three-digit issue number and a kebab-case title. When an issue has not been loaded yet, the skill reads .claude/commands/load-issues.md; make sure that project instruction file is available.

What it helps with

  • turn a GitHub issue into a technical specification
  • inspect code related to an issue
  • draft implementation and test plans
  • list files that need changes
  • save issue specifications with a consistent name

Example prompts for the agent

  • Use analyze-issue for GitHub issue #$ARGUMENTS.
  • Create a technical specification for issue #$ARGUMENTS with analyze-issue.
  • Review issue #$ARGUMENTS, inspect the code, and save the specification.

How to install analyze-issue

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/analyze-issue/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/analyze-issue/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about analyze-issue

How do I install analyze-issue in Claude Code?

Run npx skills add NeoLabHQ/context-engineering-kit --skill analyze-issue -a claude-code. Then run npx skills add NeoLabHQ/context-engineering-kit --skill analyze-issue -a claude-code again. The skill file is at ~/.claude/skills/analyze-issue/SKILL.md.

What does analyze-issue do?

It turns a GitHub issue into a saved technical specification by reviewing requirements, project code, and structure. The document includes implementation steps and a test plan in ./specs/issues/.

Does the GitHub issue need to be loaded first?

No. The skill first looks for an issue file in ./specs/issues/; if it is missing, it follows .claude/commands/load-issues.md to retrieve and store the issue details.

Similar skills

All skills for Git and GitHub →
github-issue-creator microsoft Converts voice notes, raw logs, and screenshots into structured GitHub-flavored markdown issue reports. Saves them directly to /issues/ in your repository. 63installs gh-issue-sync mitsuhiko Syncs GitHub Issues into local Markdown files for triage, search, editing, and issue creation from an editor or terminal. CX Codex +1 23,300installs oss-issue-triage Samuel Berthe Designs an issue and pull-request triage system sized to what a maintainer team can actually sustain: labels, intake, response targets, duty rotation. CX Codex +1 10,400installs create-github-issue-feature-from-specification official github This skill turns a specification file into a GitHub issue, checking for similar issues first. Use it when a feature request should cover the complete specification. 8,900installs issue-fields-migration official github Move repository label metadata or Project V2 field values into GitHub issue fields. Use it when adopting structured issue metadata. 1,900installs write-issue tldraw Enforces GitHub issue formatting and triage standards based on the tldraw repository. It helps draft clear titles, structure descriptions, and manage labels. CX Codex +1 405installs

From the same set64

git-worktrees Teaches your AI coding assistant to manage multiple linked Git working trees. Helpful for handling hotfixes, PR reviews, and parallel builds without stashing changes. CX Codex +1 1,200installs actualize Checks an FPF knowledge base against Git changes and flags evidence or decisions that may need review. Use it before new work or after repository changes. CX Codex +1 1,200installs create-hook The skill scans your project and suggests hooks for your stack: type checks, formatting, linting, tests. Then it writes the script and tests it. CX Codex +1 1,200installs create-pr Opens draft pull requests through the GitHub CLI using repository templates. It checks for uncommitted changes and formats PR titles with emojis. CX Codex +1 1,200installs apply-anthropic-skill-best-practices A skill that walks you through Anthropic's official skill-authoring rules while you build your own. Useful once a skill file grows past a few screens. CX Codex +1 1,200installs create-agent Scaffolds autonomous subagents for Claude Code with valid YAML frontmatter, isolated contexts, and triggering examples. CX Codex +1 1,200installs do-competitively Runs three agents on the same task in parallel, scores their output with judges, then synthesizes the best result. Built for work where quality beats speed. CX Codex +1 1,200installs plan-do-check-act Walks your agent through four PDCA phases: plan, do, check, act. Useful when you want to improve a process instead of guessing at it. CX Codex +1 1,200installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor