What is gh-assign-issues?

A GitHub issue assignment workflow for moving issues to a milestone or assigning them to owners in bulk. A milestone is a named group of work, often tied to a release.

Use it to retarget listed CodeWhale issues to an existing milestone, assign owners, or do both without changing labels, comments, or issue status.

It prevents issues from being assigned to the wrong release or person by checking the exact target and verifying every change.

gh-assign-issues — Skill for Claude Code and Codex by Hmbown/CodeWhale

About the project

Hmbown/CodeWhale is an open-source coding agent that runs in the terminal and is written in Rust. Developers use it to inspect repositories, edit files, run commands, and coordinate work with configurable model providers, skills, MCP servers, and approval controls; the catalogue entries extend its available workflows.

Hmbown/CodeWhale · 41,099 stars · on GitHub · codewhale.net

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Hmbown/CodeWhale --skill gh-assign-issues

Clone the repo

git clone --depth 1 https://github.com/Hmbown/CodeWhale

Made for: Claude Code, Codex.

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/hmbown/codewhale/gh-assign-issues/github.svg)](https://agentmods.dev/skills/hmbown/codewhale/gh-assign-issues)

Your own site

<a href="https://agentmods.dev/skills/hmbown/codewhale/gh-assign-issues"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/gh-assign-issues/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/hmbown/codewhale/gh-assign-issues"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/gh-assign-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,025 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. Third-party audits

Snyk pass 7 Sept 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00024	$0.01025
Opus 5.5	$0.00010	$0.00410
Sonnet 5.5	$0.00005	$0.00205
Haiku 4.5	$0.00002	$0.00103

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

Security

Grade A, and why

gh-assign-issues 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 27d ago.

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.

docs/skills/gh-assign-issues/SKILL.md · 93 lines

How it starts

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

gh-assign-issues

Retarget or assign a set of Codewhale issues to a milestone and/or owners in bulk, verifying every one. The milestone (or assignee) change is the signal; do not narrate it with comments. Use gh for all GitHub calls.

When to use

You have a concrete list of issue numbers (e.g. from triage) to move into a release milestone such as the current vX.Y.Z, or to assign to owners.
A milestone was renamed/created and its issues need re-pointing.
You finished grouping the inbox and want the queue to reflect it without posting public chatter.

This skill changes milestone/assignee only. It does not close, label, comment, merge, or release. Those stay with the maintainer.

Workflow

Confirm the exact milestone title. gh issue edit --milestone matches by name, so a typo silently fails (or worse, no-ops). Read the real titles and note the starting open-count:
```
gh api repos/Hmbown/CodeWhale/milestones \
  --jq '.[] | "\(.number)\t\(.title)\topen=\(.open_issues)\tstate=\(.state)"'
```
Copy the title string verbatim (e.g. the live vX.Y.Z title). If the target milestone is missing or closed, stop and ask the maintainer; do not create one.
Pre-flight each number. gh issue edit will happily retarget a PR or a closed issue, so screen first. The url reveals PR-vs-issue (/pull/ vs /issues/); skip anything not OPEN or that is a PR:
```
for N in <N1> <N2> <N3>; do   # substitute the real issue numbers
  gh issue view "$N" --repo Hmbown/CodeWhale \
    --json number,state,url,milestone \
    --jq '"\(.number)\t\(.state)\t\(.url)\tmilestone=\(.milestone.title // "none")"'
done
```
Flag any row whose url contains /pull/ (it is a PR) or whose state is not OPEN, and exclude it from the loop below.

Apply the change, one issue at a time, reporting per-issue success. Use --milestone, --add-assignee, or both:

for N in <N1> <N2> <N3>; do   # substitute the real issue numbers
  if gh issue edit "$N" --repo Hmbown/CodeWhale \
       --milestone "<milestone>" >/dev/null 2>&1; then
    echo "ok   #$N -> <milestone>"
  else
    echo "FAIL #$N (PR? closed? bad milestone title?)"
  fi
done
# owners: add --add-assignee handle (do not invent logins)

Read the full file on GitHub · 93 lines

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.

27d ago Changed bd9469c36a75
1mo ago Changed 660625e88162
1mo ago First seen · 93 lines · 24 tokens per session scan A 6fe631c1175c

Subscribe to this mod's changes

gh-assign-issues is a skill published in the GitHub repository Hmbown/CodeWhale (41,099 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 1,025 once invoked, about $0.0001 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-30.

Git and workflow Project management Rust agent-orchestration ai-agent cli coding-agent tui

gh-assign-issues

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

gh-assign-issues

When to use

Workflow

What this file has done since we first saw it

Other skills, from other repositories

cw-gates

cw-land

cw-orient

github

cw-dogfood

cw-slice