analyze-issue SKILL.md skillA
analyze-issue from jerseycheese/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jerseycheese/agent-skills/analyze-issue@git:20261016.04e815bPins git:20261016.04e815b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jerseycheese/agent-skills
- Path
skills/analyze-issue/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261016.04e815b, committed Oct 16, 2026
- First version recorded
- Jun 28, 2026
- Size
- 4,070 bytes
- Repository stars
- 3
- License
- MIT
Turns one GitHub issue into an implementation-ready tech spec: existing patterns, scope boundaries, a plan, and MVP tests. Use before starting work on an issue. Trigger on: "analyze issue #X", "spec out #123", "break down this issue", "plan issue #N".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Issue Analysis ## 1. Get the issue number The user will provide an issue number. If they described an issue by name instead, find it: ```bash gh issue list --search "[keywords]" --json number,title | head -5 ``` ## 2. Fetch full issue context ```bash gh issue view [NUMBER] --json number,title,body,labels,comments,createdAt,milestone,assignees ``` Read every comment — they often contain updated requirements, implementation constraints, or scope decisions that aren't in the original body. ## 3. Discover existing patterns Before planning anything, find what already exists in the codebase. Don't assume new code is needed. ```bash # Find related components by keyword grep -r "[relevant term]" src/ --include="*.ts" --include="*.tsx" -l | head -10 # Check for similar features find src/ -name "*.ts" -o -name "*.tsx" | xargs grep -l "[related concept]" | head -5 ``` Look for: - Existing components that could be extended - Utilities that could be reused - Types or interfaces to build on - Patterns established by similar features ## 4. Analyze requirements From the issue body and comments, extract: - The core problem being solved …
Read the whole file at its exact version.
How to install
mdr add jerseycheese/agent-skills/analyze-issue@sha256:c64cb5afe7f061f3The line at the top of this page pins the label git:20261016.04e815b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_55rq2e26gw4st3zs)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 28, 2026 and Oct 16, 2026, about one every 110 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.04e815b latest | 2026-10-16 | 04e815b | 4,070 B | A | view · diff |
| git:20260628.9366aee | 2026-06-28 | 9366aee | 4,267 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4070 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jerseycheese/agent-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_55rq2e26gw4st3zs GET https://markdownregistry.com/api/v1/resolve?ref=jerseycheese/agent-skills/analyze-issue GET https://markdownregistry.com/api/v1/blob/c64cb5afe7f061f382dabbe908d157d452e36eb4f77227ce650248b7d6eb198a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.