New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Gh Issue

by TypedDevs in TypedDevs/bashunit

Fetch GitHub issue, create branch, plan and implement with TDD, then open PR

MITAuto-check: notesTesting & QA

Install Gh Issue

skills CLI
$ npx skills add TypedDevs/bashunit --skill gh-issue -a claude-code

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

GitHub CLI
$ gh skill install TypedDevs/bashunit gh-issue --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/TypedDevs/bashunit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/gh-issue .claude/skills/gh-issue && 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-issue
GitHub stars
434
Token cost
~721 tokens
SKILL.md length
280 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Fetch GitHub issue, create branch, plan and implement with TDD, then open PR

  • Works in 4 steps: Setup → Plan → Implement → …
  • Tasks that involve Test-driven development
  • SKILL.md covers Arguments, Instructions and Output Format
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gh Issue is an agent skill from TypedDevs/bashunit. Fetch GitHub issue, create branch, plan and implement with TDD, then open PR

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test-driven development and Git workflow. It works with GitHub and Bash. The repository describes itself as: A simple yet powerfull testing library for bash scripts. The licence is MIT.

When your agent uses it

  • Tasks that involve Test-driven development
  • Tasks that involve Git workflow

Example prompts

  • “/gh-issue”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Edit, Write, Grep, Glob, Agent, WebFetch

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Setup
  2. Plan
  3. Implement
  4. Ship

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Edit
    • Write
    • Grep
    • Glob
    • Agent
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Gh Issue loads about 721 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 280 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Edit, Write, Grep, Glob, Agent, WebFetch

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 TypedDevs/bashunit at commit 8f297fb, republished under its MIT licence (© TypedDevs). 280 words, ~721 tokens.

Download SKILL.mdSave it as .claude/skills/gh-issue/SKILL.md (or your agent's skills folder).
name
gh-issue
description
Fetch GitHub issue, create branch, plan and implement with TDD, then open PR
allowed-tools
Bash, Read, Edit, Write, Grep, Glob, Agent, WebFetch
user-invocable
true
argument-hint
<issue-number>

GitHub Issue Workflow

Fetch a GitHub issue, create branch, implement following TDD, and open a PR.

Arguments

  • $ARGUMENTS - Issue number (e.g., 42 or #42)

Instructions

Phase 1: Setup

  1. Parse the issue number from $ARGUMENTS (strip # if present)

  2. Fetch issue details:

    bash
    gh issue view <number> --json title,body,labels,assignees,milestone,state

  3. Assign yourself if unassigned:

    bash
    gh issue edit <number> --add-assignee @me

  4. Add appropriate labels if the issue doesn't have them:

    • bug - Something isn't working
    • enhancement - New feature or request
    • documentation - Improvements or additions to documentation

  5. Create a branch from main:

    Determine prefix from labels:

    • bug → fix/
    • enhancement → feat/
    • documentation → docs/
    • Default → feat/

    Branch name: <prefix><issue-number>-<slug> (slug: lowercase title, spaces → -, max 50 chars)

    bash
    git checkout main && git pull
git checkout -b <branch-name>
Phase 2: Plan

  1. Analyze the issue: requirements, labels, referenced issues, affected areas

  2. Explore the codebase for context:

    • Find related code in src/
    • Find related tests in tests/
    • Study existing patterns

  3. Create implementation plan:

    • Acceptance Criteria
    • Test Strategy (which tests to write first)
    • Files to Change
    • Implementation Order (smallest first step)

  4. Use EnterPlanMode if implementation is non-trivial

Phase 3: Implement

  1. Follow strict TDD workflow (see @.claude/rules/tdd-workflow.md):

    For each test:

    • RED - Write failing test, verify it fails for the RIGHT reason
    • GREEN - Minimal code to pass
    • REFACTOR - Improve while keeping tests green

  2. Run full test suite frequently:

    bash
    ./bashunit tests/
./bashunit --parallel tests/

  3. Quality checks after each refactor:

    bash
    make sa && make lint
Phase 4: Ship

  1. Final verification:

    bash
    ./bashunit tests/ && ./bashunit --parallel tests/ && make sa && make lint

  2. Commit using conventional commits with Closes #<issue-number>

  3. Create PR using the /pr skill:

    /pr #<issue-number>

Output Format

After fetching, present:

## Issue #<number>: <title>

**Labels:** <labels>
**State:** <state>
**Branch:** <branch-name>

### Description
<body content>

### Next Steps
1. Explore codebase for context
2. Create implementation plan
3. Begin TDD cycle

© TypedDevs, 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 .claude/skills/gh-issue of TypedDevs/bashunit.

Open the folder on GitHubat commit 8f297fb

Compare with similar skills

Gh Issue 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.

Gh Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gh Issue this skillTypedDevs/bashunit434—~721Automated safety check: NotesMIT
Opsmill Dev Test Driving Bugsopsmill/infrahub529—~4kAutomated safety check: PassApache-2.0
Maggyalinaqi/maggy707—~1.5kAutomated safety check: PassMIT
Vulnhunter Fixcapitalone/VulnHunter1.1k1 repos~7.9kAutomated safety check: WarnApache-2.0
Bats Shell Testing Patternswshobson/agents40k11 repos~1.3kAutomated safety check: PassMIT
Auto GitHub Contributornexu-io/auto-github-contributor137—~2.5kAutomated safety check: NotesMIT

Similar skills

  • Opsmill Dev Test Driving Bugs

    opsmill/infrahub

    Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written.

    529 GitHub stars~4k tokensUpdated today
    Testing & QAAuto-check passed

  • Maggy

    alinaqi/maggy

    Maggy is a local AI engineering command center. An agent skill from alinaqi/maggy.

    707 GitHub stars~1.5k tokensUpdated 13 days ago
    Testing & QAAuto-check passed

  • Vulnhunter Fix

    capitalone/VulnHunter

    Automate vulnerability remediation from VulnHunter scan results using TDD.

    1.1k GitHub starsUsed in 1 repo~7.9k tokens
    Testing & QAAuto-check: warnings

  • Bats Shell Testing Patterns

    wshobson/agents

    Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.

    40k GitHub starsUsed in 11 repos~1.3k tokens
    Testing & QAAuto-check passed

  • Auto GitHub Contributor

    nexu-io/auto-github-contributor

    Interactively pick a quick-win contribution in any GitHub repo — either a labeled issue ("good first issue", "help wanted", docs) or a repo-scan candidate (typo, missing tests, i18n gap, actionable…

    137 GitHub stars~2.5k tokensUpdated 5 mo ago
    Testing & QAAuto-check: notes

  • Work Issue

    joesaby/astro-mermaid

    End-to-end workflow for resolving a GitHub issue in astro-mermaid — triages complexity, then runs brainstorm → TDD → implement → docs/spec → code review at the right depth.

    123 GitHub stars~891 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from TypedDevs/bashunit

All 11 skills in this repo

  • Commit

    TypedDevs/bashunit

    Stage and commit changes using conventional commits format. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~781 tokensUpdated yesterday
    Auto-check: notes

  • Gh Issues

    TypedDevs/bashunit

    Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.

    434 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check: notes

  • PR

    TypedDevs/bashunit

    Push branch and create a GitHub PR with concise, issue-linked description

    434 GitHub stars~1k tokensUpdated yesterday
    Auto-check: notes

  • Pre Release

    TypedDevs/bashunit

    Run comprehensive pre-release validation checklist. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~488 tokensUpdated yesterday
    Auto-check: notes

  • Release

    TypedDevs/bashunit

    Run pre-release validation and execute the release process. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~618 tokensUpdated yesterday
    Auto-check: notes

  • Review

    TypedDevs/bashunit

    Review a GitHub pull request; defaults to the current branch's PR when no number is given

    434 GitHub stars~449 tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Gh Issue

What does Gh Issue do?

Fetch GitHub issue, create branch, plan and implement with TDD, then open PR. Gh Issue is an agent skill from TypedDevs/bashunit.

When should I use Gh Issue?

Gh Issue fits situations like: tasks that involve Test-driven development; tasks that involve Git workflow.

How do I install Gh Issue in Claude Code?

Run `npx skills add TypedDevs/bashunit --skill gh-issue -a claude-code`. Or copy the skill folder (.claude/skills/gh-issue in TypedDevs/bashunit) into .claude/skills/gh-issue in your project. Claude Code loads it when a task matches its description.

How do I install Gh Issue in Codex?

Run `npx skills add TypedDevs/bashunit --skill gh-issue -a codex`. Or copy the skill folder (.claude/skills/gh-issue in TypedDevs/bashunit) into .agents/skills/gh-issue in your project. Codex loads it when a task matches its description.

Can I use Gh Issue 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 TypedDevs/bashunit --skill gh-issue -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-issue, .gemini/skills/gh-issue, .github/skills/gh-issue and .opencode/skills/gh-issue in your project.

What does Gh Issue need to run?

SKILL.md names no scripts, command-line tools or credentials: Gh Issue is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Edit, Write, Grep, Glob, Agent, WebFetch.

Does Gh Issue access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gh Issue safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Gh Issue use?

Gh Issue 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 Gh Issue use?

About 721 tokens (SKILL.md is roughly 2.9k 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 Gh Issue?

Skills that share tags, products or a category with Gh Issue: Opsmill Dev Test Driving Bugs (opsmill/infrahub, 529 stars), Maggy (alinaqi/maggy, 707 stars), Vulnhunter Fix (capitalone/VulnHunter, 1.1k stars) and Bats Shell Testing Patterns (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gh Issue?

TypedDevs (a GitHub organization) maintains it in TypedDevs/bashunit, which has 434 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.

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