CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/bug-report-template

Builds a well-formed bug (defect) report from raw observation notes - fills in summary, environment, steps to reproduce, expected vs actual, and severity rationale - and validates that each field has the load-bearing content reviewers and engineers need to triage. Also converts a single test-failure record (JUnit XML, Allure JSON, pytest log, Playwright report) into a classified, ready-to-file bug spec, and provides the adversarial review checklist that gates a report before it enters the tracker (required fields, single-description title test, severity-priority independence, reproduction quality). Use when a stakeholder reports a problem informally, when a CI failure artefact needs to become a triageable report, or when a drafted report needs a pre-filing quality audit.

81

0.88x
Quality

95%

Does it follow best practices?

Impact

80%

0.88x

Average score across 10 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-6/

{
  "context": "Reconstructed helpdesk notes in which the patient says 'it never works', 'it worked on Tuesday', and 'the third attempt did come down but it was empty' - three mutually inconsistent frequency claims - with no browser, no OS, no document identifier, and a family member's successful attempt of unknown provenance. Predicted baseline failure: the agent writes a clean, sympathetic report that picks the strongest claim, records the failure as consistently reproducible, invents a browser and an operating system for 'the computer in the back room', and states that the downloaded file was a zero-byte or corrupt PDF - a technical characterisation the patient never gave and her agent explicitly could not confirm.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Deliverable exists at the exact path",
      "description": "A markdown file exists at reports/results-letter-download.md covering this report. Any other path scores zero.",
      "max_score": 5
    },
    {
      "name": "MUST NOT record the failure as consistently reproducible",
      "description": "Nobody at Brightpath has reproduced this, the agent has no test patient, and the patient's own accounts conflict. Full points if the document states that the failure rate is unestablished and that no internal reproduction has been attempted, while recording the one countable data point the patient gave (three consecutive attempts, the third produced a file). Scores zero if the document asserts the download always fails, or supplies any rate or percentage the notes do not contain.",
      "max_score": 30
    },
    {
      "name": "All three frequency statements are surfaced together",
      "description": "Full points if 'it never works', 'it worked on Tuesday', and the three-attempt account all appear in the document and are presented as an unresolved conflict to be settled with the patient. Scores zero if only one is carried forward. Scores at most half if two appear or if they are listed without being identified as contradictory.",
      "max_score": 22
    },
    {
      "name": "'Empty' is quoted, not translated into a technical claim",
      "description": "The patient said 'there was nothing in it' and could not confirm whether the file opened; her son opened it. Full points if the document preserves her words, notes that the observation is second-hand, and lists establishing what the file actually contained as an action. Scores zero if the document states the file was zero bytes, blank, corrupt, or an invalid PDF, or otherwise characterises the file in terms the source does not contain.",
      "max_score": 20
    },
    {
      "name": "No invented environment",
      "description": "There is no browser, no browser version, no operating system, no device, and no document or appointment identifier in the notes, and the patient declined to read anything from her screen. Full points if each is carried as unobtainable-so-far with that reason. Scores zero if any browser, version, OS, or document identifier is asserted.",
      "max_score": 20
    },
    {
      "name": "Family member's attempt marked as not comparable",
      "description": "The agent explicitly did not establish whose account, which machine, or which letter. Full points if the document records those three unknowns and declines to treat the successful download as evidence that the account or the document is fine. Scores zero if it is presented as a clean control case or used to conclude the issue is local to the patient's machine.",
      "max_score": 14
    },
    {
      "name": "Source reliability is stated",
      "description": "The notes were reconstructed from memory after the fact, with no recording, across two calls. Full points if the document says so, so the review knows the provenance of every quoted statement. Omitting this scores zero.",
      "max_score": 12
    },
    {
      "name": "Outstanding questions listed for the next patient contact",
      "description": "The document itemises what must be asked or observed next - browser and OS, which letter, what the file contained, how many attempts, whether a supported remote session is possible. Full points for a specific list; generic 'follow up' scores at most half; nothing scores zero.",
      "max_score": 12
    }
  ]
}

SKILL.md

tile.json