gh-issue-planner 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-issue-planner 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-issue-planner@git:20261007.a584088Pins git:20261007.a584088 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-issue-planner/SKILL.md- Versions recorded
- 9
- Latest version
- git:20261007.a584088, committed Oct 7, 2026
- First version recorded
- Apr 25, 2026
- Size
- 11,049 bytes
- Repository stars
- 7
- License
- MIT
Fetch a GitHub Issue by ID using the gh CLI, investigate related code, propose a structured response plan (policy, impact scope, implementation steps), and post the agreed plan as a comment on the issue. Implementation/PR creation is out of scope — use gh-issue-resolver for that. Use when the user provides a GitHub Issue ID or asks to investigate/analyze/plan a GitHub Issue. Triggers include issue IDs like #42 or 'issue 42', requests such as Issueを調査して / Issueの対応方針を立てて, analyze issue #N, plan…
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 Issue Planner ## Overview Fetch a GitHub Issue, analyze its content, investigate related code in the repository, and present a structured response plan to the user. After the user confirms, post the agreed plan as a comment on the issue. Implementation and PR creation are out of scope — use `gh-issue-resolver` for those steps (or `gh-batch-runner` when several Issues ship together). Several Issues may be planned in one pass. The agreed-plan granularity never changes: **one comment per Issue**, so every downstream skill keeps reading exactly one plan per Issue. See *Step 7*. ## Workflow ### Step 1: Fetch the Issue Run the following command (replace `<id>` with the issue number): ```bash gh issue view <id> --json number,title,body,labels,assignees,state,url,comments ``` When several Issue numbers were given, run this once per Issue and keep the results side by side — the investigation in Step 3 is shared, the plans in Step 4 are not. If no repository context is clear, also run: ```bash gh repo view --json nameWithOwner ``` Extract from the response: - **Title** and **body**: the core problem statement …
Read the whole file at its exact version.
How to install
mdr add northraystudio/maruda/gh-issue-planner@sha256:66f4d2e7dae90dfdThe line at the top of this page pins the label git:20261007.a584088, 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_odbgzpiv53spx5v3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Apr 25, 2026 and Oct 7, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.a584088 latest | 2026-10-07 | a584088 | 11,049 B | A | view · diff |
| git:20261007.6126503 | 2026-10-07 | 6126503 | 9,954 B | A | view · diff |
| git:20261007.c71d404 | 2026-10-07 | c71d404 | 10,854 B | A | view · diff |
| git:20261007.f8d1c6f | 2026-10-07 | f8d1c6f | 9,759 B | A | view · diff |
| git:20261007.8df5aa6 | 2026-10-07 | 8df5aa6 | 9,732 B | A | view · diff |
| git:20260919.2a16c51 | 2026-09-19 | 2a16c51 | 8,169 B | A | view · diff |
| git:20260919.20d77cb | 2026-09-19 | 20d77cb | 7,916 B | A | view · diff |
| git:20260715.5b2139c | 2026-07-15 | 5b2139c | 5,100 B | A | view · diff |
| git:20260425.c2605cb | 2026-04-25 | c2605cb | 4,388 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 (11049 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_odbgzpiv53spx5v3 GET https://markdownregistry.com/api/v1/resolve?ref=northraystudio/maruda/gh-issue-planner GET https://markdownregistry.com/api/v1/blob/66f4d2e7dae90dfdea3035c9d20a6325fff8662013a2baa088a2bbde6d821a6c
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