report-to-issues SKILL.md skillA
report-to-issues from ymd38/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ymd38/dev-skills/report-to-issues@git:20261022.b7d9ef6Pins git:20261022.b7d9ef6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ymd38/dev-skills
- Path
skills/report-to-issues/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261022.b7d9ef6, committed Oct 22, 2026
- First version recorded
- Apr 6, 2026
- Size
- 6,055 bytes
- Repository stars
- 7
- License
- MIT
Parses reports generated by the software-evaluation, vulnerability-scan or sakuda-triage skills and interactively registers selected tasks as GitHub Issues using the `gh` CLI. Use when the user wants to convert an evaluation report (docs/evaluation/*.md) or security audit report (docs/security-audit/*.md) into GitHub Issues. Triggers on requests like "create issues from report", "register tasks to GitHub", "convert report to issues", or when pointing at a specific report file.
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
## Workflow ### Phase 1: Locate Report 1. If the user specifies a file path, use it directly. 2. Otherwise, list available reports: - `docs/evaluation/` — software-evaluation reports - `docs/security-audit/` — vulnerability-scan reports, and sakuda-triage reports (`sakuda-triage.*.md`, same format — only confirmed findings have `### V-XX` sections) - Skip `docs/security-audit/rule-proposals.*.md` — those are rule proposals from `rule-proposer`, not findings - If multiple exist, ask the user to select one. 3. Detect report type by content: - Contains `## Improvement Roadmap` → **evaluation report** - Contains `## Remediation Priority` → **security-audit report** --- ### Phase 2: Extract Tasks **Evaluation report** — extract rows from `## Improvement Roadmap` tables (P0–P3): Each row yields: - `priority`: P0 / P1 / P2 / P3 - `title`: Problem column (first sentence or file:line prefix) - `problem`: full Problem cell - `solution`: Solution cell - `expected_outcome`: Expected Outcome cell **Security-audit report** — extract from `## Remediation Priority` table AND individual `## Findings` sections: Each row yields: - `priority`: P0 / P1 from Priority column …
Read the whole file at its exact version.
How to install
mdr add ymd38/dev-skills/report-to-issues@sha256:927ad26997b132dfThe line at the top of this page pins the label git:20261022.b7d9ef6, 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_l6uheihmcgyyuniw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 6, 2026 and Oct 22, 2026, about one every 66 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.b7d9ef6 latest | 2026-10-22 | b7d9ef6 | 6,055 B | A | view · diff |
| git:20260919.20d77cb | 2026-09-19 | 20d77cb | 5,808 B | A | view · diff |
| git:20260406.393d9bd | 2026-04-06 | 393d9bd | 4,537 B | A | view · diff |
| git:20260406.90357d5 | 2026-04-06 | 90357d5 | 4,606 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 (6055 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
ymd38/dev-skills · 7 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l6uheihmcgyyuniw GET https://markdownregistry.com/api/v1/resolve?ref=ymd38/dev-skills/report-to-issues GET https://markdownregistry.com/api/v1/blob/927ad26997b132df95f96928a6484bf28e6100cc85c7827d357f4d1472f705d4
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.
More from ymd38/dev-skills
Every file in ymd38/dev-skills