Git:analyze Issue
Analyze a GitHub issue and create a detailed technical specification
Install
$ agentstack add skill-antifragiletech-antifragile-claude-code-analyze-issue ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-antifragiletech-antifragile-claude-code-analyze-issue) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Please analyze GitHub issue #$ARGUMENTS and create a technical specification.
Follow these steps:
- Check if the issue is already loaded:
- Look for the issue file in
./specs/issues/folder - File naming pattern:
-.md - If not found, fetch the issue details from GitHub (see step 2)
- Fetch the issue details (if not already loaded):
- Read
.claude/commands/load-issues.mdto understand how to fetch issue details - Save the issue file following the load-issues.md format
- Understand the requirements thoroughly
- Review related code and project structure
- 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
- [Step 1]
- [Step 2]
- [Step 3]
Test Plan
- Unit Tests:
- [test scenario]
- Component Tests:
- [test scenario]
- 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/-.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)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AntifragileTech
- Source: AntifragileTech/antifragile-claude-code
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.