File Bug
Create a GitHub issue for a bug row in docs/bugs.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing bug row, or asks 'create issue for bug #N', 'file bug 115', 'mirror bug 42 to GH', 'this bug needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/bugs.md` row because it lacks `GH: #N`. Stays strictly in the mirror-an-existing-row scope — do not use for triaging new bugs (that's the triage skill) or fixing bugs (that's fix-issue).
Install
npx skills add lllyys/vreader --skill file-buggit clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/file-bug ~/.claude/skills/file-bugPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# File Bug Issue
Create a GitHub issue mirroring an existing row in `docs/bugs.md`, then update that row's Notes column with `GH: #N` so the PreToolUse mirror hook stops blocking edits to it. Single tool flow that prevents the "issue created, row not updated" failure mode.
## Input
Parse the user's request to extract a single integer bug ID (e.g. from `/file-bug 115`, `file bug #115`, or `mirror bug 115 to GH`). If the user did not name an ID, ask before proceeding.
## Phase 0 — Pre-flight
1. **Argument check**: parse `$ARGUMENTS` as a single integer bug ID.
- Empty / non-numeric → print usage:
`/file-bug <bug-id> e.g. /file-bug 115`
and STOP.
2. **`gh` auth check**: run `gh auth status` (any remote). If unauthenticated → print
`gh CLI is not authenticated. Run \`gh auth login\` first.` and STOP.
3. **Repo check**: run `gh repo view --json nameWithOwner -q .nameWithOwner` from inside the project. If it errors → print `Not inside a GitHub repo (no upstream remote). gh repo set-default may help.` and STOP.
4. **Row lookup**: `grep -n "^| <id>[ |]" docs/bugs.md | head -1`. If empty → print `Bug #<id> not found in docs/bugs.md` and STOP.
5. **Existing-issue check**: read the matching row's Notes column. If it already contains `GH: #N`, print `Bug #<id> already has GH: #N — nothing to do.` and STOP cleanly (idempotent).
## Phase 1 — Build the issue
From the row, extract:
- `title` (cell 2)
- `area` (cell 3)
- `priority` (cell 4)
- `status` (cell 5)Details
- Skill name
file-bug- Repository
- lllyys/vreader
- Path
.claude/skills/file-bug/SKILL.md- Repo updated
- 6 August 2026
FAQ
What does the File Bug skill do?
Create a GitHub issue for a bug row in docs/bugs.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing bug row, or asks 'create issue for bug #N', 'file bug 115', 'mirror bug 42 to GH', 'this bug needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/bugs.md` row because it lacks `GH: #N`. Stays strictly in the mirror-an-existing-row scope — do not use for triaging new bugs (that's the triage skill) or fixing bugs (that's fix-issue).
How do I install the File Bug skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill file-bug. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is File Bug popular?
It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.
Related skills
AI Coding Agents
49lllyys/vreader
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
Dispatch
49lllyys/vreader
Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.
Feature Workflow
49lllyys/vreader
Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud
Offer Guarantee
49Liamrjohnston/offer-master-skill
Designs one fair, capped guarantee aimed at the buyer's main fear. Picks the type, sets the measure, conditions and cap, writes the exact words and claim steps, and costs it if 1 in 10 claim.
Dfx Analyze
49hw-native-sys/simpler
Analyze an onboard run's performance/scheduling/dependency/dump data using simpler's BUILT-IN DFX tools (simpler_setup.tools.*) instead of hand-rolling instrumentation. Use AFTER an onboard run when you need per-run device timing (Total/Orch/Sched), AICPU scheduler-overhead / Tail-OH breakdown, the task dependency graph, scope ring-fill peaks, or to inspect args dumps. These are simpler's own tools (shipped in the wheel), distinct from any cross-repo workload. Reach for this before writing custom timing/logging into the runtime.
Offer Included
49Liamrjohnston/offer-master-skill
Builds the core of an offer on real proof. Writes the one line promise and the week one win, builds what's included from buyer obstacles, cuts the extras and adds only bonuses that kill doubts.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.