--- name: bug-report description: Triage a user-pasted bug report (from Discord, Slack, GitHub, etc.) about the Gradient Bang game. READ-ONLY — investigates the codebase and produces TWO things in one response: (1) a compact **bug summary** (verdict, why, fix, evidence with file:line citations) the user can keep for their records or paste into Notion, and (2) a separate **Discord reply** of only 1–2 friendly sentences at the very bottom that the user can paste straight back to the reporter in the Discord channel. This skill NEVER edits code, writes files in the project, deploys, runs migrations, or makes any system changes — the deliverable is always written output only. Usage `/bug-report `. Use this skill WHENEVER the user pastes or forwards a bug report, player complaint, or feedback message and wants to know "is this real?" or "help me triage this" — even if they don't explicitly say "triage". --- # Triage Bug Report Turn a raw, possibly-messy user report into a grounded verdict and a paste-ready summary for the team. ## Read-only — written output is the ONLY deliverable This skill **never edits code or changes any state**. The user is triaging, not fixing. Specifically, do not: - Edit, create, or delete any file in the repo (code, configs, prompts, migrations, tests — nothing) - Run `git` commands that mutate state (commit, push, checkout, reset, stash pop, branch, etc.) - Deploy, restart the bot, apply migrations, or touch Supabase - Run tests, build scripts, or package installs - Call any MCP tool that changes remote state (e.g., PR creation, issue posting, Slack/Discord messages) The **only** write operation this skill performs is producing the triage summary as text in the chat. If you catch yourself about to write to a file in the project, stop — that's out of scope. If the user wants the fix implemented, they'll say so in a follow-up; this skill ends with the summary. Read-only investigation is fine: Read, Grep, Glob, `Explore` subagents, `git log` / `git diff` / `git status`, etc. ## Why this exists Bug reports from Discord/Slack/GitHub/email come in all shapes — some are real bugs, some are misunderstandings of game mechanics, some are feature requests dressed as bugs, some are noise. The goal of this skill is to save the user from having to manually dig through the codebase each time and to give their team a consistent, terse format. ## Input The user pastes the report in the slash-command args (or in chat). It may be: - A single message or a long thread - Contain screenshots references, timestamps, usernames, emojis — leave those alone - Be in broken English, all-lowercase, etc. Don't "fix" the report. Just triage it. ## Step 1 — Extract the core claim Read the report and distill it into **one sentence** stating what the reporter claims is happening. If the report mixes several complaints, pick the most concrete one and note the others for the "Related" field. If you genuinely can't extract a claim, skip to the `Needs more info` verdict. ## Step 2 — Investigate with parallel Explore agents Spawn **2–3 `Explore` subagents in parallel** (single message, multiple tool calls) to ground-truth the claim against the codebase. Tailor each agent's focus to the report — good default splits: - **Agent A — Server/DB**: relevant Supabase edge functions in `deployment/supabase/functions/` and shared queries in `_shared/pg_queries.ts`. Does the reported behavior match what the server actually does? - **Agent B — Client/UI**: relevant React components in `client/app/src/`. Is the UI actually rendering what the reporter says it is (or isn't)? - **Agent C — Bot / agents**: `src/gradientbang/pipecat_server/` if the report involves the voice agent or task agents. Drop agents that clearly don't apply. For a report that's obviously UI-only, one Explore agent is fine — don't spawn agents just for symmetry. Give each agent a focused prompt, the reporter's claim, and a word budget (~400 words). Ask specifically: *does the code behave the way the reporter describes, and if not, what does it actually do?* ## Step 3 — Decide the verdict Pick exactly one: - **Real bug** — the code does not do what it should, and the reporter's description is consistent with that gap. You can point at the specific file/line that's wrong or missing. - **Not a bug** — the code behaves as intended. This is a misunderstanding of game mechanics, a UX complaint (feature request), or the reporter is mistaken about what happened. - **Needs more info** — you can't tell from the code alone. Specify exactly what would resolve the ambiguity (repro steps, timestamp, character name, screenshot of a specific panel, etc.). Err on the side of **Needs more info** over guessing. "I couldn't confirm this from the code" is more useful to the team than a wrong verdict. ## Step 4 — Produce the output (two parts) Every response has **two clearly separated parts**: 1. **Bug summary** — starts with a **bold descriptive title** on its own line (so the whole block is self-identifying when pasted into Notion), then the grounded triage with file:line evidence. 2. **Discord reply** — a short 1–2 sentence message the user can paste straight back to the reporter in a Discord channel. Both parts go in the same response. The Discord reply is always at the bottom, under a visible divider, so the user can copy just that part cleanly. ### Writing the title The first line of the summary is **always a short descriptive bold title** — not the generic word "Bug summary". Treat it like a commit subject: under ~70 chars, starts with a noun phrase, names the actual problem. The user pastes this straight into Notion as the bug's heading. - Good: `**Destroyed corp ships leak into fleet listings**` - Good: `**Leaderboard hides players outside top 100**` - Good: `**Top-bar icon buttons & zoom slider lack accessible names**` - Bad: `**Bug summary**` (generic — doesn't identify which bug) - Bad: `**A bug where the leaderboard doesn't show...**` (too long, not scannable) ### Formatting rules - **No `#` / `##` / `###` headers anywhere.** Discord renders those as oversized banners, and the user's Notion works fine with bolded labels. - **Plain markdown only**: `**bold**`, bullet hyphens, backticks for file paths. - **No "Original report" quote-back.** The reporter already wrote it; repeating wastes space. - Start the response directly with the **bold title** — no preamble, no "Here's what I found:", no generic "Bug summary" label. ### Template — ALWAYS use this exact structure ``` **** **Verdict:** **Why:** **Fix:** first"> **Evidence:** - `path/to/file.ts:123` — - `path/to/other.ts:45` — *(optional — skip if one bullet is enough)* --- **Discord reply** *(paste this to the reporter)* > <1–2 sentences, terse, addressed to the reporter. Give the verdict in plain English. No file paths, no jargon, no affirmations, no fix commitments.> ``` For **Needs more info**, replace the `Fix:` + `Evidence:` lines with: ``` **Ask the reporter for:** ``` …and write the Discord reply as a short friendly request for those details. ### Discord reply — tone guide Terse and human. Just state the outcome. - **No affirmations.** Skip "good catch", "thanks for flagging", "really appreciate it", "absolutely right", etc. The reporter doesn't need to be thanked for reporting; they need an answer. - **No hedging softeners.** Skip "just to confirm", "so it turns out", "looks like maybe". State what's true. - **Acknowledge, don't commit to fixes.** Confirm whether the issue is real, but don't promise the fix will ship. Use "we'll look into it" / "we'll take a look" / "on our radar" — NOT "we'll add", "we'll fix it", "we're shipping a fix". The triage identifies the issue; whether/when it ships is the team's call, not this skill's. - **One or two sentences, max.** If you can say it in one, do. - **Plain English.** No file paths, no `aria-describedby`, no "the BFS caps at 100 hops" — translate technical findings into what the reporter experiences. - **No emojis** unless the reporter's own message used them. Think of it as a matter-of-fact note from a teammate, not a customer-service reply. ### Examples **Real bug:** ``` **Leaderboard hides players outside top 100** **Verdict:** Real bug **Why:** Players outside the top 100 are simply absent from the leaderboard — no rank, no row, no indication they exist. **Fix:** Pin the current player's row to the bottom of each category when they're outside the top 100. **Evidence:** - `deployment/supabase/functions/leaderboard_resources/index.ts:135` caps each category at 100 rows with no "me" row appended. - `client/app/src/components/panels/LeaderboardPanel.tsx:199` already has the styling for the current player — it just has nothing to render when they're below the cutoff. --- **Discord reply** *(paste this to the reporter)* > Confirmed bug — the leaderboard only renders the top 100, so anyone below doesn't show up at all. We'll look into pinning your own row to the bottom so your real rank is visible. ``` **Not a bug:** ``` **Warp power "resets" after relogin** **Verdict:** Not a bug **Why:** Warp power is persisted in the DB and reloaded on login — the "disappearing" effect is the recharge timer resetting the display, not lost state. **Fix:** Working as intended. Optional polish: clearer tooltip on the warp-power bar. **Evidence:** - `deployment/supabase/functions/login/index.ts` reloads `warp_power` from the `ships` table on every login. - `deployment/supabase/functions/recharge_warp_power/index.ts` is the only path that mutates it. --- **Discord reply** *(paste this to the reporter)* > Not a bug — warp power persists across logins; what resets visually is the recharge animation, not the value. ``` **Needs more info:** ``` **"Trading is broken" — not enough detail to reproduce** **Verdict:** Needs more info **Why:** "Trading is broken" is too vague to ground-truth against the code — could be a specific port, a UI issue, or a price calc. **Ask the reporter for:** the sector/port, what they tried to buy or sell, the exact error or unexpected result, and an approximate timestamp. --- **Discord reply** *(paste this to the reporter)* > Need a bit more to reproduce: which port, what you tried to buy or sell, and what the error or unexpected result was. ``` ## Principles - **Don't speculate.** If the code doesn't show it, say so. A `Needs more info` verdict with a clear ask is more useful than a confident guess. - **Cite specific files and line numbers.** The user's team needs to be able to verify your verdict in seconds. - **Always deliver both parts.** Bug summary on top for the user's records, Discord reply at the bottom for pasting to the reporter. Never skip one. - **Discord reply is for the reporter, not the team.** Addressed to the person who filed the report. Terse, human, no jargon, no file paths, no affirmations ("good catch" / "thanks for flagging"), no hedging softeners, and **no fix commitments** ("we'll add X", "we'll fix it") — use "we'll look into it" / "on our radar" instead. Technical detail lives in the summary above. - **No `##` headers.** Use bold labels instead — works in both Discord and Notion. - **Written output is the only deliverable.** See the "Read-only" section at the top. No file edits, no deploys, no DB writes, no git mutations. If the triage reveals a clear fix, *describe* it in the `Fix:` line — don't apply it. --- Source attribution: pipecat-ai Original project: https://github.com/pipecat-ai/gradient-bang/blob/5735d794ea69527526761cb305b91b8244ce4c58/.claude/skills/bug-report/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: pipecat-ai Original project: https://github.com/pipecat-ai/gradient-bang/blob/5735d794ea69527526761cb305b91b8244ce4c58/.claude/skills/bug-report/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Sales Roles: Customer Success Manager, Game Developer, QA / Test Engineer Specialties: Testing Tools: Discord, GitHub, Notion, Slack Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: eb82d70d5db2b410314791b6d7cb030e6c3af892196ad439b837cc77f275b1e9