A GitHub issue-to-pull-request workflow for the Plumb Rust workspace. It guides work from investigation and planning through implementation, tests, review, CI, and cleanup; TDD means writing tests before the related code.

Handling one or more related GitHub issues, optionally in an isolated worktree, while recording implementation, review, commit, pull-request, and CI status.

It gives multi-step issue work a defined process and keeps progress available when a session is interrupted or resumed.

How aram-devdocs/plumb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to aram-devdocs/plumb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/aram-devdocs/plumb/main/.agents/skills/gh-issue/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/aram-devdocs/plumb

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aram-devdocs/plumb/gh-issue/github.svg)](https://agentmods.dev/skills/aram-devdocs/plumb/gh-issue)

Your own site

<a href="https://agentmods.dev/skills/aram-devdocs/plumb/gh-issue"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/gh-issue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aram-devdocs/plumb/gh-issue"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/gh-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,468 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00059	$0.03468
Opus 5.5	$0.00024	$0.01387
Sonnet 5.5	$0.00012	$0.00694
Haiku 4.5	$0.00006	$0.00347

Measured 2mo ago against content hash ef6bcc6b95ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gh-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/gh_issue_run.py, scripts/validate_skill.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/gh-issue/SKILL.md · 288 lines

How it starts

The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/gh-issue — GitHub issue delivery lifecycle for Plumb

Strict delivery lifecycle that drives one or more GitHub issues from investigation through merged PR against aram-devdocs/plumb.

Use /gh-runbook first when the source is a runbook spec that still needs to be fanned out into grouped issues.

Usage

/gh-issue 17                     # Single issue
/gh-issue 17 18 19               # Multiple related issues (single PR)
/gh-issue 17 --worktree          # Isolated worktree
/gh-issue 17 --resume            # Resume after compaction

State management

# Initialize a new run
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py init-run <primary> <slug> [--issues 17 18 19] [--worktree]

# Update phase or field
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py update-state <primary> <slug> --phase implementing
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py update-state <primary> <slug> --pr 42
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py update-state <primary> <slug> --review spec pass
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py update-state <primary> <slug> --commit abc1234

# Validate a run can be resumed
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py validate-resume <primary> <slug>

# Poll PR CI status
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py poll-pr <primary> <slug>

# Clean up worktree after done
python3 .agents/skills/gh-issue/scripts/gh_issue_run.py cleanup-worktree <primary> <slug>

Phases

investigating > planning > bootstrapped > implementing > verifying > reviewing > pr > waiting-ci > cleanup > done

Lifecycle

Phase 1 — investigating

Fetch issue(s):

gh issue view <N> --repo aram-devdocs/plumb --json number,title,body,labels,milestone,assignees,comments

Identify affected crates, layers, and files via codebase exploration.
Read the root AGENTS.md, the scoped AGENTS.md for any crate touched (crates/plumb-*/AGENTS.md), and .agents/rules/ — the Plumb invariants live there.
Check for blocking dependencies (issues referenced in body).
If the issue came from a runbook spec, re-read the spec in docs/runbooks/ to confirm batch and gate context.

Initialize run state:

python3 .agents/skills/gh-issue/scripts/gh_issue_run.py init-run <primary> <slug> --issues <N> [<M>...]

Read the full file on GitHub · 288 lines

Files

What ships with it

14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 288 lines · 59 tokens per session scan A ef6bcc6b95ed

Subscribe to this mod's changes

gh-issue is a skill published in the GitHub repository aram-devdocs/plumb (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 3,468 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow TDD Testing chromium cli css design-system design-tokens developer-tools

extract-design

Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…

Manavarya09/design-extract · 140 tokens

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

bench-fixture-gen

Generates the shared per-task fixture that every competing arm starts from: a realistic dataset plus an image asset base. Fairness rule: fixtures are generated ONCE per task by this preprocessor and sealed (sha256) before any arm runs; arms never generate their own.

kwakseongjae/oh-my-design · 0 tokens

test-then-commit

Implements a small change and commits it. Use when the user asks for a quick fix with a commit.

Goldziher/ai-rulez · 28 tokens

am-command-build

Implement the next task incrementally — build, test, verify, commit.

sampleXbro/agentsmesh · 18 tokens

ensemble-full-implement-trd

This command implements a complete Technical Requirements Document (TRD) using modern git-town feature branch workflow. It creates a feature branch and delegates to ensemble-orchestrator which routes to tech-lead-orchestrator for structured TDD-based development including planning, implementation, testing, and quality…

FortiumPartners/ensemble · 65 tokens

plumb: Skill for Claude Code