{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "bug-report",
  "name": "Bug report",
  "category": "Technical",
  "summary": "Turn a defect narrative into a report a developer can triage.",
  "use_cases": [
    "Issue descriptions",
    "User-reported defects"
  ],
  "word_count": 146,
  "url": "https://sho.rten.it/methods/bug-report/",
  "instructions_url": "https://sho.rten.it/methods/bug-report/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/bug-report/SKILL.md",
  "json_url": "https://sho.rten.it/methods/bug-report/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/bug-report/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#bug-report",
  "skill_name": "bug-report",
  "skill_description": "Turn a defect narrative into a report a developer can triage. Use for Issue descriptions, User-reported defects.",
  "agents_md_url": "https://sho.rten.it/methods/bug-report/AGENTS.md",
  "sources": [],
  "instructions": "Condense the supplied defect report for a developer who must understand its scope. Use this for a complete issue description; use a reproduction procedure when only ordered steps are needed.\n\nLead with the failing behavior and its trigger. Separate observed behavior from expected behavior. Group environment, versions, frequency, and affected inputs into short supporting lines. Include the shortest supplied reproduction path and any workaround that actually worked.\n\nKeep exact error text, identifiers, relevant permissions, and tested boundaries. A successful control case limits the claim; do not turn one failure into a statement about all users or platforms. Keep uncertainty about the cause. Remove frustration, repeated observations, and unrelated troubleshooting history.\n\nOutput a specific title and brief sections for Reproduce, Expected, Actual, and Scope. Add a workaround only when supplied. Omit empty fields. Do not diagnose the cause, invent missing steps, or say a fix was verified.",
  "example": {
    "context": "Profile editor defect",
    "before": "I am using Profile Desk 3.8 in Firefox 128 on Ubuntu 24.04. Every time I try to save my profile after selecting a 3 MB PNG avatar, the Save button keeps showing a spinner and the profile never updates. I tried this three times and got the same result each time. I would expect the profile to save and show the new avatar. To do it, open Profile, select the PNG, and press Save. A 200 KB JPEG saved successfully. I do not know whether this is a browser issue or a server issue.",
    "after": "Profile Desk 3.8: Save hangs with a 3 MB PNG avatar\n\nReproduce: Open Profile, select the 3 MB PNG, then press Save.\nExpected: Save the profile and show the new avatar.\nActual: The spinner continues; the profile does not update.\nScope: 3/3 attempts in Firefox 128 on Ubuntu 24.04. A 200 KB JPEG saved successfully. Cause unknown.",
    "must_preserve": [
      "Profile Desk 3.8; Firefox 128; Ubuntu 24.04",
      "3 MB PNG; 3/3 failures",
      "Exact reproduction path and expected avatar update",
      "Spinner continues and profile does not update",
      "200 KB JPEG succeeded; cause unknown"
    ],
    "kind": "illustrative",
    "omitted": [
      "First-person narration and the repeated statement that every save attempt had the same result."
    ]
  }
}