issue-analyze SKILL.md skillA
issue-analyze from sd0xdev/sd0x-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sd0xdev/sd0x-harness/issue-analyze@git:20260905.7f65168Pins git:20260905.7f65168 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sd0xdev/sd0x-harness
- Path
skills/issue-analyze/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260905.7f65168, committed Sep 5, 2026
- First version recorded
- Mar 5, 2026
- Size
- 16,199 bytes
- Repository stars
- 194
- License
- MIT
GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified analysis + verdict assessment + investigation strategy.
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 Analyze Skill ## Trigger - Keywords: analyze issue, investigate problem, problem analysis, root cause, root cause analysis, triage review, review thread analysis ## Input Types | Type | Source | Example | |------|--------|---------| | GitHub Issue | Issue number, URL, or description | `/issue-analyze 123` | | Review Thread | file:line + reviewer comment | `/issue-analyze --triage "src/foo.ts:42 — Use early return"` | When input is a **Review Thread**: - Phase 1 skips `gh issue view`, uses provided thread data directly - Phase 2 classification uses Review Thread dimensions (see `references/classification.md`) ## Modes | Mode | Input Type | Phases Executed | Use Case | |------|-----------|----------------|----------| | Full (default) | Issue or Thread | 1 → 2 → 2.5 → 3 → 4 | Deep analysis with investigation | | Triage (`--triage`) | Review Thread | 2 → 2.5 only | Lightweight classification + verdict (thread data provided inline) | | Triage (`--triage`) | GitHub Issue | 1 → 2 → 2.5 | Fetch issue first, then classify + verdict | ## When NOT to Use - Known root cause, fix directly (use `/bug-fix`) - Pure feature development (use `/feature-dev`) …
Read the whole file at its exact version.
How to install
mdr add sd0xdev/sd0x-harness/issue-analyze@sha256:7151c18e98aa159cThe line at the top of this page pins the label git:20260905.7f65168, 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_fa2dlpk7kb6vozin)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 5, 2026 and Sep 5, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.7f65168 latest | 2026-09-05 | 7f65168 | 16,199 B | A | view · diff |
| git:20260316.68cdf5d | 2026-03-16 | 68cdf5d | 13,553 B | A | view · diff |
| git:20260305.3ae8b92 | 2026-03-05 | 3ae8b92 | 7,886 B | A | view · diff |
| git:20260305.37d4591 | 2026-03-05 | 37d4591 | 7,570 B | A | view · diff |
| git:20260305.c56d819 | 2026-03-05 | c56d819 | 7,406 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 (16199 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
sd0xdev/sd0x-harness · 194 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fa2dlpk7kb6vozin GET https://markdownregistry.com/api/v1/resolve?ref=sd0xdev/sd0x-harness/issue-analyze GET https://markdownregistry.com/api/v1/blob/7151c18e98aa159cf256676c82e0b679057adb7bf35d48ca6f69ee9d0156524b
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.