Agent skill

GitHub Issue Bulk Assigner

by codewhale-hq in codewhale-hq/Codewhale

Moves a list of GitHub issues into a milestone or assigns them to owners with the gh CLI, checking each one before and after the change.

MITAuto-check passedDevelopment

Install GitHub Issue Bulk Assigner

skills CLI
$ npx skills add codewhale-hq/Codewhale --skill gh-assign-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codewhale-hq/Codewhale gh-assign-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codewhale-hq/Codewhale.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/skills/gh-assign-issues .claude/skills/gh-assign-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gh-assign-issues
GitHub stars
41k
Token cost
~953 tokens
SKILL.md length
447 words
Files
1
Skills in repo
63
Repo updated
First seen
Licence
MIT

At a glance

Moves a list of GitHub issues into a milestone or assigns them to owners with the gh CLI, checking each one before and after the change.

  • Works in 5 steps: Confirm the exact milestone title. gh… → Pre-flight each number. gh issue edit… → Apply the change, one issue at a time,… → …
  • Moving a triaged list of issues into the current release milestone
  • SKILL.md covers When to use, Workflow and Red flags / don't
  • Calls gh

What it does

This skill retargets a known list of issue numbers to a release milestone, to owners, or both, using only the gh CLI. The change itself is the signal, so the agent posts no comments. It does not close, label, comment on, merge or release anything; those stay with the maintainer.

First the agent reads the real milestone titles and the starting open count, because a mistyped title silently does nothing, and it stops and asks if the milestone is missing or closed. It then screens every number, skipping pull requests and issues that are not open. Edits run one issue at a time with a result reported for each, and repeating them is harmless.

Afterward the agent reruns the milestone listing to confirm the open count rose by the number of issues moved, and spot-checks a few to confirm the milestone title. The commands in the skill are written for the Codewhale repository.

When your agent uses it

  • Moving a triaged list of issues into the current release milestone
  • Re-pointing issues after a milestone was renamed or recreated
  • Assigning a batch of issues to owners without posting comments
  • Making the issue queue reflect a finished round of inbox grouping

Example prompts

  • “Move the issues from this triage list into the current release milestone and verify each one.”
  • “Add the milestone to every issue in triage-list.txt and report any that fail.”
  • “Re-point the issues from the renamed milestone to the new one and confirm the open count changed.”

Requirements

  • GitHub CLI (gh), signed in and able to edit the repository's issues

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the exact milestone title. gh issue edit --milestone matches by
  2. Pre-flight each number. gh issue edit will happily retarget a PR or a
  3. Apply the change, one issue at a time, reporting per-issue success. Use
  4. Verify the milestone moved. Re-run the step-1 command and confirm the open
  5. Report a tight ledger: issues moved, issues skipped and why (PR / closed /

What it can do on your machine

Read from SKILL.md and the folder at commit 8d2fb45. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Issue Bulk Assigner loads about 953 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 447 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~953

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codewhale-hq/Codewhale at commit 8d2fb45, republished under its MIT licence (© codewhale-hq). 447 words, ~953 tokens.

Download SKILL.mdSave it as .claude/skills/gh-assign-issues/SKILL.md (or your agent's skills folder).
name
gh-assign-issues
description
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.

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

  1. 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:

    bash
    gh api repos/codewhale-hq/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.

  2. 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:

    bash
    for N in <N1> <N2> <N3>; do   # substitute the real issue numbers
      gh issue view "$N" --repo codewhale-hq/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.

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

    bash
    for N in <N1> <N2> <N3>; do   # substitute the real issue numbers
      if gh issue edit "$N" --repo codewhale-hq/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)

    Edit is idempotent: re-pointing an already-correct issue is harmless.

  4. Verify the milestone moved. Re-run the step-1 command and confirm the open count rose by the number of issues you moved in (minus any you skipped). Spot-check a few with the step-2 view to confirm milestone.title is now the target.

  5. Report a tight ledger: issues moved, issues skipped and why (PR / closed / title mismatch), the before/after open-count, and any owner assignments. No public comment is posted.

Show full SKILL.md (123 more words)Show less

Red flags / don't

  • Don't edit from a list of titles alone. Resolve to OPEN issue numbers and confirm each is an issue, not a PR (/pull/ in the url), before editing.
  • Don't guess the milestone title or assignee login. A near-miss name no-ops or fails silently; an invalid login errors mid-loop.
  • Don't post "moved to <milestone>" comments. The milestone change is the signal; extra chatter is noise to good-faith contributors.
  • Don't close, merge, label, tag, or release as part of this. Those need explicit maintainer approval (see AGENTS.md).
  • Don't skip step 4. An unmoved open-count means the title was wrong or every edit silently failed.
  • Preserve contributor credit: this skill never alters authorship, harvest markers (Co-authored-by / Harvested from PR #N), or closing references.

© codewhale-hq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in docs/skills/gh-assign-issues of codewhale-hq/Codewhale.

Open the folder on GitHubat commit 8d2fb45

Compare with similar skills

GitHub Issue Bulk Assigner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Issue Bulk Assigner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Issue Bulk Assigner this skillcodewhale-hq/Codewhale41k—~953Automated safety check: PassMIT
Cosai Ws4 Issue Triagecosai-oasis/ws4-secure-design-agentic-systems135—~1.6kAutomated safety check: PassCustom licence
GitHub Project Management Swarmruvnet/agentic-flow8196 repos~7.1kAutomated safety check: PassNone
Issue Triagesuperset-sh/superset15k—~995Automated safety check: PassCustom licence
A2ui Issue Triagea2ui-project/a2ui17k—~1.5kAutomated safety check: PassApache-2.0
MAUI Issue Triage Sessiondotnet/maui23k—~2kAutomated safety check: PassMIT

Similar skills

  • Cosai Ws4 Issue Triage

    cosai-oasis/ws4-secure-design-agentic-systems

    CoSAI WS4 only — draft a structured triage note for a WS4/ADLC issue or PR in @parmarmanojkumar's house format.

    135 GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.

    819 GitHub starsUsed in 6 repos~7.1k tokens
    Product & Project ManagementAuto-check passed
  • Issue Triage

    superset-sh/superset

    Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels, milestone, and assignee.

    15k GitHub stars~995 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Runs an interactive triage session over open dotnet/maui GitHub issues, presenting them one at a time and suggesting milestones through bundled PowerShell scripts.

    23k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Shift Issue Writer

    shift-editor/shift

    Sets the rules for finding, writing and updating Shift GitHub issues: search for duplicates first, use outcome-focused titles and testable acceptance criteria.

    348 GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from codewhale-hq/Codewhale

All 63 skills in this repo
  • Codewhale Dogfood Install

    codewhale-hq/Codewhale

    Proves a Codewhale change in the real product: a stamped release build, an atomic local install, fresh-shell verification and manual QA that automated gates cannot cover.

    41k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Codewhale Session Handoff

    codewhale-hq/Codewhale

    Writes a paste-ready handoff for the next agent session, opening with a state-check command block and separating done, suspected and blocked work.

    41k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Sub-Agent Delegation

    codewhale-hq/Codewhale

    Guides when and how to split multi-step coding, research or verification work into focused sub-agent runs while the parent keeps integration and final checks.

    41k GitHub stars~790 tokensUpdated today
    Auto-check passed
  • Codewhale Fleet Manager

    codewhale-hq/Codewhale

    Triages and manages Codewhale fleet runs and workers with typed commands, classifying failures and choosing a safe restart, resume or escalation.

    41k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Codewhale Issue Filing

    codewhale-hq/Codewhale

    Turns a bug or idea into a single actionable Codewhale GitHub issue with evidence, a gap-naming title, acceptance criteria and related links.

    41k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Works with

Questions about GitHub Issue Bulk Assigner

What does GitHub Issue Bulk Assigner do?

Moves a list of GitHub issues into a milestone or assigns them to owners with the gh CLI, checking each one before and after the change. This skill retargets a known list of issue numbers to a release milestone, to owners, or both, using only the gh CLI. The change itself is the signal, so the agent posts no comments.

When should I use GitHub Issue Bulk Assigner?

GitHub Issue Bulk Assigner fits situations like: moving a triaged list of issues into the current release milestone; re-pointing issues after a milestone was renamed or recreated; assigning a batch of issues to owners without posting comments; making the issue queue reflect a finished round of inbox grouping.

How do I install GitHub Issue Bulk Assigner in Claude Code?

Run `npx skills add codewhale-hq/Codewhale --skill gh-assign-issues -a claude-code`. Or copy the skill folder (docs/skills/gh-assign-issues in codewhale-hq/Codewhale) into .claude/skills/gh-assign-issues in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issue Bulk Assigner in Codex?

Run `npx skills add codewhale-hq/Codewhale --skill gh-assign-issues -a codex`. Or copy the skill folder (docs/skills/gh-assign-issues in codewhale-hq/Codewhale) into .agents/skills/gh-assign-issues in your project. Codex loads it when a task matches its description.

Can I use GitHub Issue Bulk Assigner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codewhale-hq/Codewhale --skill gh-assign-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gh-assign-issues, .gemini/skills/gh-assign-issues, .github/skills/gh-assign-issues and .opencode/skills/gh-assign-issues in your project.

What does GitHub Issue Bulk Assigner need to run?

Going by SKILL.md and its folder, GitHub Issue Bulk Assigner needs the command-line tools its instructions call (gh). Our summary lists: GitHub CLI (gh), signed in and able to edit the repository's issues.

Does GitHub Issue Bulk Assigner access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub Issue Bulk Assigner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Issue Bulk Assigner use?

GitHub Issue Bulk Assigner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Issue Bulk Assigner use?

About 953 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Issue Bulk Assigner?

Skills that share tags, products or a category with GitHub Issue Bulk Assigner: Cosai Ws4 Issue Triage (cosai-oasis/ws4-secure-design-agentic-systems, 135 stars), GitHub Project Management Swarm (ruvnet/agentic-flow, 819 stars), Issue Triage (superset-sh/superset, 15k stars) and A2ui Issue Triage (a2ui-project/a2ui, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issue Bulk Assigner?

codewhale-hq (a GitHub organization) maintains it in codewhale-hq/Codewhale, which has 41,078 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on October 9, 2026.

Source: codewhale-hq/Codewhale on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.