kid-sid/claude-spellbook/github-issues
Claude Code and agent skill by kid-sid/claude-spellbook
- community
Checking that the SKILL.md file is still in the repository.
Use when creating, triaging, or filing GitHub issues — writing bug reports, feature requests, or task tickets; classifying severity; using the gh CLI; or handling edge cases like regressions, flaky failures, security vulnerabilities, or cross-repo dependencies.
Install
npx vskill@latest install kid-sid/claude-spellbook/github-issuesSKILL.md
GitHub Issues
Write issues that are acted on — not ignored, misrouted, or reopened for missing info.
When to Activate
- Filing a bug report, feature request, or engineering task on GitHub
- Triaging an issue and assigning severity or priority
- Using the
ghCLI to create or manage issues programmatically - Handling special cases: regressions, flaky tests, security holes, data-loss bugs
- Writing acceptance criteria or reproduction steps
- Linking issues across repositories or to pull requests
Issue Types & When to Use Each
| Type | Label | Use When | Must Include | |
|---|---|---|---|---|
| Bug | bug | Observed behavior differs from documented or expected | Repro steps, expected vs actual, environment | |
| Regression | bug, regression | Previously working behavior broke in a specific version | Commit/PR that introduced it, last-good version | |
| Feature | enhancement | New capability that doesn't exist yet | Problem statement, proposed solution, AC | |
| Task / Chore | chore | Non-feature engineering work (refactor, migration, upgrade) | Why now, success criteria, estimated scope | |
| Performance | performance | Measurable slowdown or resource regression | Benchmark before/after, profiling output | |
| Security | (private) | Vulnerability, auth bypass, data exposure | Do NOT file publicly — use private advisory | |
| Documentation | documentation | Missing, wrong, or outdated docs | Affected page/file, what's wrong, correct behavior | |
| Flaky Test | flaky, ci | Test fails intermittently with no code change | Failure frequency, CI run links, log excerpts |
Severity × Priority Matrix
Severity = impact if it occurs. Priority = urgency to fix.
| High Priority | Low Priority | ||
|---|---|---|---|
| High Severity | P0: fix immediately, page oncall | P1: fix this sprint | |
| Low Severity | P2: schedule soon, workaround exists | P3: backlog, good first issue |
P0 triggers: data loss, auth bypass, production down, PII exposure, charge errors. P1 triggers: feature broken for >1% of users, no workaround, SLA at risk.
Add severity to issue title: [P0], [P1], etc. for anything P1 and above.
gh CLI Reference
Bug Report Template
TypeError: Cannot read property 'status' of undefined at handleChargeError (payments.ts:214) ...
Feature Request Template
Regression Bug: Extra Requirements
A regression needs more than a standard bug report:
git bisect start git bisect bad HEAD git bisect good v2.3.0
... binary search ...
c8d1e4f is the first bad commit
Always run git bisect before filing a regression — "it worked before" without a commit is not actionable.
Flaky Test: Extra Requirements
FAIL src/payments/__tests__/charge.test.ts ● PaymentService › charge › handles decline Expected: "declined" Received: undefined at Object.<anonymous> (charge.test.ts:42)
Security Vulnerabilities: Do NOT File Publicly
Security issues must stay private until a patch is released and deployed. Coordinated disclosure: notify maintainer → agree on fix timeline → publish advisory.
Performance Issues: Extra Requirements
GET /api/v1/reports/monthly p50=120ms p95=340ms p99=890ms (k6: 50 VUs, 5 min, 1000 req/min)
GET /api/v1/reports/monthly p50=1200ms p95=4100ms p99=timeout
Linking Issues and PRs
Use Fixes only in the PR/commit that resolves the issue — not in the issue itself.
Duplicate Detection Before Filing
If a duplicate exists:
- If open: add a comment with your reproduction details, don't file a new issue
- If closed and regressed: reopen with a comment linking the regression context
Labels Reference
| Label | Meaning | |
|---|---|---|
bug | Confirmed behavior defect | |
regression | Was working, now broken | |
enhancement | New capability | |
chore | Maintenance, no user-visible change | |
documentation | Docs only | |
performance | Measurable slowdown | |
flaky | Intermittent test failure | |
security | Vulnerability (use sparingly on public repos) | |
good first issue | Isolated, well-scoped, beginner-friendly | |
needs-triage | Filed but not yet classified | |
needs-repro | Cannot reproduce without more info | |
wontfix | Intentional behavior or out of scope | |
blocked | Waiting on another issue or external dependency | |
breaking-change | Fix or feature changes existing behavior |
Edge Cases
Issue Spans Multiple Repositories
Create a tracking issue in the primary repo:
File sub-issues in each repo, link back to the tracker.
Breaking Change
A fix that itself breaks existing behavior needs two issues:
- The bug issue (what's broken now)
- A separate
breaking-changeissue documenting the behavior change, migration path, and which major version it ships in
Issue Has Insufficient Information
Add needs-repro label and comment:
Data-Loss Bug
Always P0. Beyond the standard bug template:
- Quantify scope: how many records, which users, time window
- Identify if the data is recoverable (backups, event log, audit trail)
- Document any immediate mitigation applied
Issue is Actually a Support Request
Close with:
Cross-Platform Bug (Only Fails on Windows/Linux)
Red Flags
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/github-issues/skill.md
Popularity
- Repository stars
- 186
- Repository forks
- 15
- 7-day trend score
- 26
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kid-sid/claude-spellbook/github-issues)