--- title: "Bug Receipt: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/skills/github-bug-receipt/ description: "Creates an evidence-bearing defect or incident handoff that distinguishes verified, partial and blocked outcomes." --- # Bug Receipt: review, setup & limitations · Undominated.ai > Creates an evidence-bearing defect or incident handoff that distinguishes verified, partial and blocked outcomes. [← Explore all skills](/skills/) TESTING AND RELIABILITY / GitHub community # Bug Receipt Creates an evidence-bearing defect or incident handoff that distinguishes verified, partial and blocked outcomes. See setup guidance ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-22 Evidence 10 linked sources Publisher GitHub community Licence MIT ↗ Revision a19b3101cc79 Read what was—and wasn’t—checked ↓ “Close defects and incidents with a BUG RECEIPT and VERIFIED, PARTIAL, or BLOCKED status after diagnosis, repair, or recovery.” GitHub community · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Requires the observed baseline, root-cause evidence, changed artifacts and relevant checks to accompany a completion status. - A bundled JSON contract and validator reject structurally inconsistent receipts, including a verified status with declared gaps. ### A good fit for - Handing a repaired defect to another developer or reviewer - Making incident recovery evidence and unresolved verification gaps easy to inspect ### Weigh up before choosing - The validator checks supplied fields and status consistency; it cannot prove that a command actually ran or that a claimed observation is correct. - A receipt may use executed, supplied or mixed evidence. Keep that distinction visible rather than presenting supplied reports as a fresh test run. - Its prescribed response format needs adaptation where a team already has a required incident or change record. - The JSON contract requires a changed file or artifact for verified status. A no-edit recovery cannot be represented as verified without adapting the contract transparently. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - skills/bug-receipt/SKILL.md - README.md (installation and supported-host sections) - LICENSE - skills/bug-receipt/assets/receipt.template.json - skills/bug-receipt/references/receipt-contract.md - skills/bug-receipt/references/receipt.schema.json - skills/bug-receipt/scripts/validate-receipt.mjs ### Our findings - The complete definition, JSON schema, template and JavaScript validator/contract were inspected. - The supplied template starts with partial/not-run observations; the procedure requires real evidence before stronger completion wording. ### Not established by this review - No upstream definition, helper, installer or generated workload was executed. - No end-to-end agent session or effectiveness benchmark was run. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Add a skill to your workflow. Upstream setup instructions ↗ DOCUMENTED COMMAND npx skills add https://github.com/github/awesome-copilot/tree/a19b3101cc797a35de8b1c1698c13d1344703522/skills/bug-receipt --skill bug-receipt Copy command ↗ Copying does not execute this command. It may retrieve a newer version than the reviewed source. - Install the complete skill directory, including its references and helpers; select your intended host and project scope. - Review the instructions before invoking them. The source revision is pinned; the installer was not executed or version-pinned by this review. ### Before you start - Node.js/npm and git for the documented Skills installer - An agent host that supports the skill format and the tools required by the workflow - Node.js if running the bundled JSON validator ### Compatibility GitHub Copilot ### Repository instructions and host-provided tools - Read authorized defect reports, logs and test output - Write a structured receipt and supporting artifact references - Run the local receipt validator if the user chooses to execute the helper ### Cost model MIT-licensed collection; agent usage and any project testing or incident tooling costs are separate. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Definition at the reviewed revision ↗ Checked 2026-09-22 https://github.com/github/awesome-copilot/blob/a19b3101cc797a35de8b1c1698c13d1344703522/skills/bug-receipt/SKILL.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access - Publisher installation guidance ↗ Checked 2026-09-22 https://github.com/github/awesome-copilot/blob/a19b3101cc797a35de8b1c1698c13d1344703522/README.md Supports: install, compatibility - Licence at the reviewed revision ↗ Checked 2026-09-22 https://github.com/github/awesome-copilot/blob/a19b3101cc797a35de8b1c1698c13d1344703522/LICENSE Supports: license, access.cost - Reviewed companion: skills/bug-receipt/assets/receipt.template.json ↗ Checked 2026-09-22 https://github.com/github/awesome-copilot/blob/a19b3101cc797a35de8b1c1698c13d1344703522/skills/bug-receipt/assets/receipt.template.json Supports: review, limitations, install, access - Reviewed companion: skills/bug-receipt/references/receipt-contract.md ↗ Checked 2026-09-22 https://github.com/github/awesome-copilot/blob/a19b3101cc797a35de8b1c1698c13d1344703522/skills/bug-receipt/references/receipt-contract.md Supports: review, limitations, install, access - Reviewed companion: skills/bug-receipt/references/receipt.schema.json ↗ Checked 2026-09-22 https://github.com/github/awesome-copilot/blob/a19b3101cc797a35de8b1c1698c13d1344703522/skills/bug-receipt/references/receipt.schema.json Supports: review, limitations, install, access - Reviewed companion: skills/bug-receipt/scripts/validate-receipt.mjs ↗ Checked 2026-09-22 https://github.com/github/awesome-copilot/blob/a19b3101cc797a35de8b1c1698c13d1344703522/skills/bug-receipt/scripts/validate-receipt.mjs Supports: review, limitations, install, access - Skills installer: README.md ↗ Checked 2026-09-22 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md Supports: install - Skills installer: src/git.ts ↗ Checked 2026-09-22 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/git.ts Supports: install - Skills installer: src/source-parser.ts ↗ Checked 2026-09-22 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts Supports: install KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Superpowers Verification Before Completion ↗ Requires a fresh command result or direct check for each completion claim and distinguishes passing tests from fulfilling requirements.](/skills/obra-verification-before-completion/)[### Diagnosing Bugs ↗ A debugging procedure that establishes a reproducible symptom, tests competing explanations and preserves a regression check.](/skills/mattpocock-diagnosing-bugs/)[### Superpowers Receiving Code Review ↗ Checks review feedback against the code and project constraints before making and testing each requested change.](/skills/obra-receiving-code-review/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)