Home / northraystudio / maruda · skills/gh-issue-planner/SKILL.md · GitHub

gh-issue-planner skillA

Name: gh-issue-planner
Author: northraystudio

This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.

gh-issue-planner is agent-read markdown (skill) from northraystudio/maruda: 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 is.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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

Latest version

mdr add northraystudio/maruda/gh-issue-planner@git:20260919.2a16c51

Exact content

mdr add northraystudio/maruda/gh-issue-planner@sha256:867263e39b153d3f

Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.

Badge

[![mdr](https://markdownregistry.com/badge/art_odbgzpiv53spx5v3.svg)](https://markdownregistry.com/a/art_odbgzpiv53spx5v3)

1 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260919.2a16c51 latest	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

A 17 of 17 checks passed. Deterministic, no model, same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (8169 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

GitHub

northraystudio/maruda · 4 stars · license MIT · pushed 2026-09-19 · 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/867263e39b153d3f22ac86c59c87b8299cbc6c0ec17069405cb72fedc5733d04

Your agent 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.

More from northraystudio/maruda

data-validation skill

northraystudio/maruda · skills/data-validation/SKILL.md · Inspect a project's data for correctness and produce a read-only validation report — record counts, NULL rates, value…