file-buglisted

# File Bug Turn "here's what's going wrong" into a GitHub issue that lets whoever picks it up **understand what happened and figure out how it happened** — without having to come back and ask the reporter for basics. ## The one rule that defines this skill **Your job is to capture, not to cure.** Do not design, propose, or implement a fix. Do not root-cause to a code change. You may record a *suspected area* in Context if you genuinely observed evidence for it, but never frame the issue around a solution. The person who picks up the issue owns the diagnosis and the fix. ## Issue format (always) The issue **body** uses exactly these three sections, in this order: ```markdown ## What actually happened <the observed behavior — concrete, specific, what the user/system did and saw> ## What should have happened <the expected behavior — what the user expected instead> ## Context <everything the next person needs to understand and reproduce it — see below> ``` The **title** is a short, specific summary of the symptom (not the fix). Good: `Comment anchor jumps to wrong paragraph after deleting a list item`. Bad: `Fix anchor bug` / `Anchors broken`. ## Workflow ### 1. Get the report If the user already described what's wrong, use that. If they invoked the skill with no description, just ask them — openly — what went wrong (e.g. "What happened? Describe it however's easiest."). **Do not ask them to categorize it, pick a type, or answer setup questions first.** They came to r