analyze-issue

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha c64c9eb3b29e · 26 Oct 2026Report an issue or request a re-scan

• Publisherneolabhq GitHub organizationOwner of the repository this skill is read from
• Source folderneolabhq/context-engineering-kit/skills/analyze-issueThe exact folder we audited
• LicenceGPL-3.0As the repository states it
• Commit pinned for this verdictc64c9eb3b29eA new audit runs when the source changes
• Repository statusNot archivedLast push 60 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Analyze a GitHub issue and create a detailed technical specification

---
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
- [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)

Excerpt, first 2,228 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/neolabhq/context-engineering-kit
git -C context-engineering-kit checkout c64c9eb3b29e

Works in

1. 2026-10-26
   ✓SAFE B 89 / 100

   first audit · source c64c9eb3b29e

Questions about analyze-issue

• github.com/neolabhq/context-engineering-kit/tree/master/skills/a — the audited source at commit c64c9eb3b29e and every finding aboveObserved · 26 Oct 2026

Spotted something wrong? Report a correction · Methodology