Stats
Actions
Tags
From bugscribe
Use this skill when the user hands you one already-identified bug to file as GitHub issue against one specific repository.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bugscribe:submit-an-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Target GitHub repository named by user.
Target GitHub repository named by user. Refuse when user hands in no concrete bug.
Clone or pull default branch before writing report. Verify symptom against source code before writing.
Do not run build, tests, linters, or static analysis. Do not modify files, create branches, or open pull requests.
Check open issues for duplicate before filing. Discard report when it matches already-open issue. Check closed issues too for same symptom.
Use short declarative title naming symptom and location.
Write body as few short paragraphs.
Cover bug, why it is wrong, and proposed fix.
Read examples/ directory.
Mirror its title shape, structure, and tone.
Keep body compact.
Never use Markdown headings in body or comment.
Write like human.
Avoid AI cadence, boilerplate openings, and buzzword strings.
Never add Generated with footers or Co-Authored-By AI trailers.
Never add robot emoji.
Include file path and approximate line number for offending code. Quote offending code as snippet whenever source is available. Let snippet show defect, since code beats prose.
Suggest concrete fix in one or two sentences. Do not propose refactors, rewrites, or sweeping redesigns. Do not attach patches, diffs, or pull requests to issue. Do not invent reproduction steps or fabricate stack traces. Do not claim to have run program.
Attach bug label to issue when account can label issues.
Skip label when account lacks that permission.
Read .github/CODEOWNERS to find repository owner.
Take account from global * entry as repository owner.
Fall back to slug owner when .github/CODEOWNERS is absent.
For organizations, treat top recent committer as owner.
Identify authenticated account before deciding on follow-up comment.
When owner is authenticated account, file issue and stop.
Never post follow-up comment to yourself.
Never @-mention authenticated account.
When owner is someone else, @-mention owner in one follow-up comment.
Offer to clarify in that comment.
Keep comment to one or two sentences.
Ping one account.
Never request deadline.
Stop after follow-up comment.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub yegor256/bugscribe --plugin bugscribe