create-github-issues SKILL.md skillA
create-github-issues from pjt222/agent-almanac is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pjt222/agent-almanac/create-github-issues@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/create-github-issues/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0, committed Aug 17, 2026
- First version recorded
- Apr 19, 2026
- Size
- 7,466 bytes
- Repository stars
- 43
- License
- MIT
Structured GitHub issue creation from review findings or task breakdowns. Groups related findings into logical issues, applies labels, and produces issues with standard templates including summary, findings, and acceptance criteria. Designed to consume output from review-codebase or similar review skills.
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
# Create GitHub Issues Structured GitHub issue creation from review findings or task breakdowns. Converts a list of findings (from `review-codebase`, `security-audit-codebase`, or manual analysis) into well-formed GitHub issues with labels, acceptance criteria, and cross-references. ## When to Use - After a codebase review produces a findings table that needs tracking - After a planning session identifies work items that should become issues - When converting a TODO list or backlog into trackable GitHub issues - When batch-creating related issues that need consistent formatting and labeling ## Inputs - **Required**: `findings` — a list of items, each with at minimum a title and description. Ideally also includes: severity, affected files, and suggested labels - **Optional**: - `group_by` — how to batch findings into issues: `severity`, `file`, `theme` (default: `theme`) - `label_prefix` — prefix for auto-created labels (default: none) - `create_labels` — whether to create missing labels (default: `true`) - `dry_run` — preview issues without creating them (default: `false`) ## Procedure ### Step 1: Prepare Labels Ensure all needed labels exist in the repository. …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/create-github-issues@sha256:7668127d931c53e8The line at the top of this page pins the label v1.0, 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_gnybzwipgswhccuk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 19, 2026 and Aug 17, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-17 | a784899 | 7,466 B | A | view · diff |
| v1.0 | 2026-06-05 | 33b561c | 7,437 B | A | view · diff |
| v1.0 | 2026-04-23 | bc66d7e | 7,433 B | A | view · diff |
| v1.0 | 2026-04-19 | e334ebd | 7,472 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 (7466 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
pjt222/agent-almanac · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gnybzwipgswhccuk GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/create-github-issues GET https://markdownregistry.com/api/v1/blob/7668127d931c53e854ee38f02830a99448a44e848a9e83393b2adff57c681463
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.