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

Official agent skill

Bug Receipt

by github in github/awesome-copilot

Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.

OfficialMITAuto-check passed

Install Bug Receipt

skills CLI
$ npx skills add github/awesome-copilot --skill bug-receipt -a claude-code

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

GitHub CLI
$ gh skill install github/awesome-copilot bug-receipt --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/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bug-receipt .claude/skills/bug-receipt && 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
bug-receipt
GitHub stars
40k
Token cost
~1.1k tokens
SKILL.md length
491 words
Files
5 (incl. scripts, references, assets)
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.

  • Works in 4 steps: Follow the live owner path from input to… → Separate observed facts, bounded… → Require a concrete location or runtime… → …
  • SKILL.md covers Mandatory closeout output, Establish the evidence boundary, Trace and repair and Close the proof loop, plus 2 more sections
  • Runs JavaScript scripts from its folder; calls node

What it does

Bug Receipt is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/receipt.template.json`, `references/receipt-contract.md` and `references/receipt.schema.json`).

The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

Example prompts

  • “/bug-receipt”

Requirements

  • Node.js

Workflow steps

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

  1. Follow the live owner path from input to symptom.
  2. Separate observed facts, bounded inferences, and gaps.
  3. Require a concrete location or runtime transition before naming root cause.
  4. Make the smallest responsible change; avoid unrelated cleanup, retries, silent fallbacks, and fixture-specific exceptions.

What it can do on your machine

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

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

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

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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 Receipt loads about 1.1k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 34 tokens; SKILL.md has 491 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.5k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 491 words, ~1,090 tokens.

Download SKILL.mdSave it as .claude/skills/bug-receipt/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
bug-receipt
description
Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.
metadata.version
1.4.1

Bug Receipt

Mandatory closeout output

For every bug or incident closeout decision, return the complete receipt below as the entire user-facing result, even when the user requests a concise reply or does not name this format. Concision shortens field values; it never removes or renames a row. Do not replace the receipt with prose.

text
BUG RECEIPT · VERIFIED | PARTIAL | BLOCKED

Problem    <observed defect and intended behavior>
Baseline   <failing interaction or command and decisive result; or not run>
Root cause <proven mechanism; or unproven hypothesis>
Change     <responsible change; or none>
Proof      <supplied or executed check: result; include every decisive layer>
Gaps       <none; or exact missing proof and single next experiment/package>
Source     executed now | supplied | mixed

Use not run, unproven, or none explicitly. Never omit a row to make the receipt look complete.

Establish the evidence boundary

Before editing, record the observed problem, intended behavior, strongest direct check, and evidence source: executed now, supplied, or mixed. Never imply that supplied evidence was executed in the current run.

Keep evidence privacy-minimal. Redact credentials, tokens, cookies, personal data, private URLs, and sensitive payloads; preserve only the identifiers and excerpts needed to reproduce or correlate the failure.

Reproduce the failure with the narrowest safe check when possible. If reproduction is unavailable, preserve the evidence obtained and cap the result at PARTIAL or BLOCKED.

Trace and repair

  1. Follow the live owner path from input to symptom.
  2. Separate observed facts, bounded inferences, and gaps.
  3. Require a concrete location or runtime transition before naming root cause.
  4. Make the smallest responsible change; avoid unrelated cleanup, retries, silent fallbacks, and fixture-specific exceptions.

Do not convert a plausible patch, stale log, source read, or passing build into proof of the user-visible behavior.

Close the proof loop

Run only checks required by the affected contract:

  • original reproduction or direct acceptance check;
  • nearest negative or regression check;
  • affected build or integration gate;
  • real UI, API, persistence, concurrency, or runtime path when the claim crosses that boundary.

Use these decisive boundaries:

SurfaceRequired direct proof
Logic or failing testOriginal failing input or focused test now passes
UI behaviorReal interaction plus relevant console and network observation
API or integrationRequest, response, and responsible service behavior
PersistenceWrite/read or reload round trip through the real owner path
Race or lifecycleRepeated concurrent trigger; zero-or-one success; affected-row and transaction evidence; final invariant
Cross-system blockerOne sanitized failing request/response with timestamp or request ID, edge and application logs, and identity-provider logs when the trace reaches that owner
Show full SKILL.md (136 more words)Show less

Assign status

  • VERIFIED: observed baseline, concrete cause, responsible change, all declared checks passed, no material gap.
  • PARTIAL: useful evidence exists, but a required proof layer is missing or inconclusive.
  • BLOCKED: a specific external condition prevents reproduction, repair, or proof.

For PARTIAL or BLOCKED, name the single minimal experiment or correlated evidence package that closes the decisive gap. Never invent a command, observation, count, location, or result.

For a machine-readable receipt or CI integration, read references/receipt-contract.md and conform to its JSON fields, evidence-source marker, compatibility rule, and status invariants.

When a JSON artifact is requested, start from assets/receipt.template.json, write it to a task-owned path, and validate it with node scripts/validate-receipt.mjs <receipt.json> from this skill directory. Do not commit the generated receipt unless the user requests it.

Source and license

Originally published at https://github.com/lMysticl/bug-receipt under the MIT License.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references, assets) in skills/bug-receipt of github/awesome-copilot.

  • SKILL.md
  • assets/receipt.template.json
  • references/receipt-contract.md
  • references/receipt.schema.json
  • scripts/validate-receipt.mjs

Open the folder on GitHubat commit 727ff2e

Compare with similar skills

Bug Receipt 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 Receipt compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bug Receipt this skillgithub/awesome-copilot40k—~1.1kAutomated safety check: PassMIT
Incident Responderdavila7/claude-code-templates32k7 repos~2.6kAutomated safety check: PassMIT
Incident Commanderalirezarezvani/claude-skills28k—~3.8kAutomated safety check: PassMIT
Incident Managementsickn33/agentic-awesome-skills47k2 repos~4.5kAutomated safety check: PassMIT
Incident Responsesickn33/agentic-awesome-skills47k1 repos~3.7kAutomated safety check: PassMIT
Incident Responsealirezarezvani/claude-skills28k—~3.8kAutomated safety check: PassMIT

Similar skills

  • Incident Responder

    davila7/claude-code-templates

    Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.

    32k GitHub starsUsed in 7 repos~2.6k tokens
    DevOps & CloudAuto-check passed

  • Incident Commander

    alirezarezvani/claude-skills

    Comprehensive incident response framework from detection through resolution and post-incident review.

    28k GitHub stars~3.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Incident Management

    sickn33/agentic-awesome-skills

    Implement incident management processes and escalation procedures.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    DevOps & CloudAuto-check passed

  • Incident Response

    sickn33/agentic-awesome-skills

    Handle security incidents with IR playbooks and procedures. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~3.7k tokens
    DevOps & CloudAuto-check passed

  • Incident Response

    alirezarezvani/claude-skills

    A skill your agent uses when a security incident has been detected or declared and needs classification, triage, escalation path determination, and forensic evidence collection.

    28k GitHub stars~3.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Building Incident Response Dashboard

    mukul975/Anthropic-Cybersecurity-Skills

    Builds real-time incident response dashboards in Splunk, Elastic, or Grafana to provide SOC analysts and leadership with situational awareness during active incidents, tracking affected systems…

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Bug Receipt

What does Bug Receipt do?

Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery. Bug Receipt is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.

How do I install Bug Receipt in Claude Code?

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

How do I install Bug Receipt in Codex?

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

Can I use Bug Receipt 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 github/awesome-copilot --skill bug-receipt -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-receipt, .gemini/skills/bug-receipt, .github/skills/bug-receipt and .opencode/skills/bug-receipt in your project.

What does Bug Receipt need to run?

Going by SKILL.md and its folder, Bug Receipt needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Bug Receipt access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Bug Receipt 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Bug Receipt use?

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

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Bug Receipt?

Skills that share tags, products or a category with Bug Receipt: Incident Responder (davila7/claude-code-templates, 32k stars), Incident Commander (alirezarezvani/claude-skills, 28k stars), Incident Management (sickn33/agentic-awesome-skills, 47k stars) and Incident Response (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Receipt?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

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