Agent skill

Bug

Report, list, or manage bug reports as GitHub issues. An agent skill from yicheng47/runner.

MITAuto-check passedTesting & QA

Install Bug

skills CLI

$ npx skills add yicheng47/runner --skill bug -a claude-code

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

GitHub CLI

$ gh skill install yicheng47/runner bug --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/yicheng47/runner.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bug .claude/skills/bug && 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/

Paste into Claude Code

Install the "bug" agent skill from https://github.com/yicheng47/runner/tree/main/.agents/skills/bug into .claude/skills/bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/yicheng47/runner/tree/main/.agents/skills/bug

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add yicheng47/runner --skill bug -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install yicheng47/runner bug --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yicheng47/runner.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/bug .agents/skills/bug && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bug" agent skill from https://github.com/yicheng47/runner/tree/main/.agents/skills/bug into .agents/skills/bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yicheng47/runner --skill bug -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install yicheng47/runner bug --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yicheng47/runner.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/bug .cursor/skills/bug && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bug" agent skill from https://github.com/yicheng47/runner/tree/main/.agents/skills/bug into .cursor/skills/bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/yicheng47/runner.git --path .agents/skills/bug

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add yicheng47/runner --skill bug -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install yicheng47/runner bug --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yicheng47/runner.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/bug .gemini/skills/bug && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "bug" agent skill from https://github.com/yicheng47/runner/tree/main/.agents/skills/bug into .gemini/skills/bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install yicheng47/runner bug

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add yicheng47/runner --skill bug -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/yicheng47/runner.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/bug .github/skills/bug && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "bug" agent skill from https://github.com/yicheng47/runner/tree/main/.agents/skills/bug into .github/skills/bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yicheng47/runner --skill bug -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install yicheng47/runner bug --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yicheng47/runner.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/bug .opencode/skills/bug && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bug" agent skill from https://github.com/yicheng47/runner/tree/main/.agents/skills/bug into .opencode/skills/bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: bug
GitHub stars: 273
Token cost: ~949 tokens
SKILL.md length: 534 words
Files: 1
Skills in repo: 4
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Report, list, or manage bug reports as GitHub issues. An agent skill from yicheng47/runner.

Works in 5 steps: Ask the user to describe the bug: what… → Investigate the codebase to confirm the… → Pick a priority (see Priority below). If… → …
Tasks that involve QA and bug reports
SKILL.md covers Usage, Labels, Priority and Notes
Calls gh

What it does

Bug is an agent skill from yicheng47/runner. Report, list, or manage bug reports as GitHub issues

Its SKILL.md is about 950 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 QA and bug reports. It works with GitHub. The repository describes itself as: Where terminal agents work together. Claude Code, Codex, Copilot CLI and pi on the same task, in one mission, each keeping its own TUI in a real terminal. The licence is MIT.

When your agent uses it

Tasks that involve QA and bug reports

Example prompts

“/bug”

Workflow steps

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

Ask the user to describe the bug: what happened, what was expected, and steps to reproduce (if known).
Investigate the codebase to confirm the area of code involved. Note relevant file paths.
Pick a priority (see Priority below). If the user didn't state one, propose one based on the bug's severity and the rubric, and confirm…
Create a GitHub Issue with labels bug and the chosen P0/P1/P2/P3
Report the issue URL and the assigned priority.

What it can do on your machine

Read from SKILL.md and the folder at commit 0aef92a. 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

Bug loads about 949 tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 534 words of instructions outside code blocks.

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

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 yicheng47/runner at commit 0aef92a, republished under its MIT licence (© yicheng47). 534 words, ~949 tokens.

Download SKILL.mdSave it as .claude/skills/bug/SKILL.md (or your agent's skills folder).

name: bug
description: Report, list, or manage bug reports as GitHub issues

Bug Reporting

Report and manage bugs for Runners via GitHub Issues with the bug label.

Usage

/bug <action> [args]

Actions

`new`

Report a new bug.

Ask the user to describe the bug: what happened, what was expected, and steps to reproduce (if known).
Investigate the codebase to confirm the area of code involved. Note relevant file paths.
Pick a priority (see Priority below). If the user didn't state one, propose one based on the bug's severity and the rubric, and confirm before filing. Don't file unlabeled.

Create a GitHub Issue with labels bug and the chosen P0/P1/P2/P3:

Title: bug: <short description>

Body using this template:

## Description
<what's wrong>

## Expected behavior
<what should happen>

## Steps to reproduce
<if known>

## Relevant code
<file paths and brief pointers to the affected area>

## Environment
- OS: <if relevant>
- Version: <app version from `crates/runner-app/Cargo.toml`>

Command shape: gh issue create --label bug --label P1 --title "…" --body "…"

Report the issue URL and the assigned priority.

`list`

Show all bugs, sorted by priority.

Fetch open bugs with priority + metadata as JSON so they can be sorted: gh issue list --label bug --state open --limit 50 --json number,title,labels,createdAt,assignees
Sort the rows by priority (P0 first, then P1, P2, P3, then unlabeled-by-priority last). Within a priority bucket, sort by createdAt ascending (oldest first — they've been waiting longest).
Present a table with columns: Priority, #, Title, Created, Assignee (if any). Use the priority label as the leading column so the ranking is visually obvious. Issues without a P-label show — in the priority column and a callout asking the user to triage them.
If the user asks for closed bugs too, repeat with --state all and add a State column.

`close <issue-number>`

Mark a bug as fixed.

Close the GitHub Issue: gh issue close <number>
Confirm closure to the user.

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

`prioritize <issue-number> <P0|P1|P2|P3>`

Set or change the priority of an existing bug.

Remove any existing P-label on the issue, then add the new one: gh issue edit <number> --remove-label P0 --remove-label P1 --remove-label P2 --remove-label P3 --add-label <priority> (Removing all four is safe — gh ignores remove-label for labels not present.)
Confirm the new priority.

`view <issue-number>`

Show details of a specific bug report.

Fetch the issue: gh issue view <number>
Display the full issue body, current priority, comments count, and state.

Labels

bug — all bug issues use this label.
P0 / P1 / P2 / P3 — priority, exactly one per issue.

Priority

Every bug gets exactly one priority label. Rubric:

P0 — Ship-blocker, data-loss risk, security issue, or recent regression breaking a load-bearing flow. Drop other work.
P1 — Real user friction in a common path; broken affordance the user sees daily. Fix this cycle.
P2 — Annoying but workaround exists; rare path; cosmetic issue in a prominent surface. Fix when convenient.
P3 — Edge case, theoretical, or "would be nice." No fixed timeline.

When in doubt between two levels, pick the lower-urgency one and say why; over-labeling P0/P1 dilutes the signal.

Notes

Do not commit or push unless the user explicitly asks.
When creating issues, investigate the codebase first to include relevant file paths — this makes bugs actionable.
Read the app version from crates/runner-app/Cargo.toml when populating the Environment section.

Files

Just SKILL.md in .agents/skills/bug of yicheng47/runner.

Open the folder on GitHubat commit 0aef92a

Compare with similar skills

Bug 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.

Bug compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bug this skillyicheng47/runner	273	—	~949	Automated safety check: Pass	MIT	today
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness	1.7k	—	~1.6k	Automated safety check: Pass	MIT	1 mo ago
Evidence-Driven Testingmichaelshimeles/skills	1.3k	1 repos	~3.9k	Automated safety check: Pass	None	4 days ago
Create GitHub IssueNVIDIA/OpenShell	15k	—	~1.7k	Automated safety check: Pass	Apache-2.0	today
Triage IssuesClickHouse/clickhouse-java	1.6k	—	~904	Automated safety check: Pass	Apache-2.0	today
Gentle AI Issue CreationGentleman-Programming/gentle-shell	1.2k	—	~2.5k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Weavebench Cua Reproduce
AMAP-ML/LongHorizon-Harness
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.
1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Evidence-Driven Testing
michaelshimeles/skills
Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.
1.3k GitHub starsUsed in 1 repo~3.9k tokens
Testing & QAAuto-check passed
Create GitHub Issue
NVIDIA/OpenShell
Official
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.
15k GitHub stars~1.7k tokensUpdated today
Testing & QAAuto-check passed
Triage Issues
ClickHouse/clickhouse-java
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
1.6k GitHub stars~904 tokensUpdated today
Testing & QAAuto-check passed
Gentle AI Issue Creation
Gentleman-Programming/gentle-shell
Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.
1.2k GitHub stars~2.5k tokensUpdated today
Testing & QAAuto-check passed
Termio Bug Report
termio-sh/termio
Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…
540 GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed

Questions about Bug

What does Bug do?

Report, list, or manage bug reports as GitHub issues. An agent skill from yicheng47/runner. Bug is an agent skill from yicheng47/runner.

When should I use Bug?

Bug fits situations like: tasks that involve QA and bug reports.

How do I install Bug in Claude Code?

Run `npx skills add yicheng47/runner --skill bug -a claude-code`. Or copy the skill folder (.agents/skills/bug in yicheng47/runner) into .claude/skills/bug in your project. Claude Code loads it when a task matches its description.

How do I install Bug in Codex?

Run `npx skills add yicheng47/runner --skill bug -a codex`. Or copy the skill folder (.agents/skills/bug in yicheng47/runner) into .agents/skills/bug in your project. Codex loads it when a task matches its description.

Can I use Bug 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 yicheng47/runner --skill bug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug, .gemini/skills/bug, .github/skills/bug and .opencode/skills/bug in your project.

What does Bug need to run?

Going by SKILL.md and its folder, Bug needs the command-line tools its instructions call (gh).

Does Bug 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 Bug 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 Bug use?

Bug 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 Bug use?

About 949 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 Bug?

Skills that share tags, products or a category with Bug: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 15k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug?

yicheng47 (a GitHub user) maintains it in yicheng47/runner, which has 273 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Bug

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bug Reporting

Usage

Actions

new

list

close <issue-number>

prioritize <issue-number> <P0|P1|P2|P3>

view <issue-number>

Labels

Priority

Notes

Files

Compare with similar skills

Similar skills

More from yicheng47/runner

Related

Questions about Bug

`new`

`list`

`close <issue-number>`

`prioritize <issue-number> <P0|P1|P2|P3>`

`view <issue-number>`