gh-batch-runner SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
gh-batch-runner from northraystudio/maruda is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add northraystudio/maruda/gh-batch-runner@git:20261007.6126503Pins git:20261007.6126503 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- northraystudio/maruda
- Path
skills/gh-batch-runner/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261007.6126503, committed Oct 7, 2026
- First version recorded
- Sep 19, 2026
- Size
- 7,831 bytes
- Repository stars
- 7
- License
- MIT
Run several planned GitHub Issues as one unit: collect them under an Epic Issue with sub-issues, implement each on a shared epic/ branch in dependency order, verify the branch as a whole, and open a single Pull Request into the integration branch. Use when the user wants several Issues fixed, verified and released together. Triggers include requests such as Issue1,2,3をまとめて対応して / まとめて修正してリリースしたい / この3件を一緒に出して, 'batch these issues', 'do issues 1 2 3 together', 'ship these issues as one release'.…
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
# GitHub Batch Runner ## Overview Implement several Issues as one release: one integration branch, one verification of the whole, one Pull Request. Per-Issue implementation follows the `gh-issue-resolver` contract unchanged — this skill owns only what is batch-level: membership, ordering, whole-branch verification, and the single PR. Use this skill only when the answer to **"do these ship together?"** is yes. Independent Issues use `gh-issue-resolver` once per Issue; a dependency chain that ships separately uses the stacked flow (also `gh-issue-resolver`, with the dependency's branch as base). ## Prerequisites - **Every member Issue has an agreed plan comment** (`<!-- gh-issue-planner:agreed-plan -->`) posted by `gh-issue-planner`. If any Issue lacks one, stop and run the planner for that Issue first — planning several Issues in one pass is supported there. - The repository's **integration branch** is known (CLAUDE.md `## Flow`; falls back to the default branch). ## Workflow ### Step 1: Collect the batch under an Epic Issue The batch's membership is an Epic Issue holding the members as sub-issues — not a branch …
Read the whole file at its exact version.
How to install
mdr add northraystudio/maruda/gh-batch-runner@sha256:0173923a713908f0The line at the top of this page pins the label git:20261007.6126503, 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_2urfqjxcyabu4yv4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 19, 2026 and Oct 7, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.6126503 latest | 2026-10-07 | 6126503 | 7,831 B | A | view · diff |
| git:20260919.2a16c51 | 2026-09-19 | 2a16c51 | 7,708 B | A | view · diff |
| git:20260919.20d77cb | 2026-09-19 | 20d77cb | 7,447 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 (7831 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
northraystudio/maruda · 7 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2urfqjxcyabu4yv4 GET https://markdownregistry.com/api/v1/resolve?ref=northraystudio/maruda/gh-batch-runner GET https://markdownregistry.com/api/v1/blob/0173923a713908f0ef90bd49032128ba56bd5554fe0d1b89eb4474850b5b8204
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 northraystudio/maruda
Every file in northraystudio/maruda