workflow-bug-triage SKILL.md skillA
workflow-bug-triage from lugassawan/swe-workbench is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lugassawan/swe-workbench/workflow-bug-triage@git:20260828.71a6399Pins git:20260828.71a6399 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lugassawan/swe-workbench
- Path
skills/workflow-bug-triage/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260828.71a6399, committed Aug 28, 2026
- First version recorded
- Jul 2, 2026
- Size
- 10,229 bytes
- Repository stars
- 3
- License
- MIT
Use when investigating a bug to root-cause and FILE a GitHub issue rather than fixing immediately — counterpart to /swe-workbench:debug (which patches). Enforces the Iron Law (no patches without root cause), and produces a structured issue with code-path table and impact assessment.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Workflow: Bug Triage (investigate + file issue) **Announce at start:** "I'm using the workflow-bug-triage skill to investigate the root cause and file a GitHub issue." ## When to invoke - The user describes a bug, defect, or unexpected behaviour and wants it documented (not fixed in-session). - Phrases: "investigate this bug", "find the root cause", "file an issue for this bug", "triage this". - The bug is in code the user does not own, or fix-planning needs to happen separately. - The investigation needs to produce a shareable artifact (an issue) other people will act on. ## When NOT to invoke - The user wants a fix **now** → use `/swe-workbench:debug` (counterpart skill that ends in code change + regression test). - The root cause is already known and only the fix is needed → use `/swe-workbench:debug`. - The user is capturing a feature request, idea, or improvement (not a bug) → use the `/swe-workbench:capture` command directly. - The user is reviewing already-merged code for retroactive issues → use `/swe-workbench:review` first. ## Iron Law **NO FIXES WITHOUT ROOT CAUSE FIRST.** If the user proposes a fix before the root cause is established, refuse politely: …
Read the whole file at its exact version.
How to install
mdr add lugassawan/swe-workbench/workflow-bug-triage@sha256:a52a26b951cd1cefThe line at the top of this page pins the label git:20260828.71a6399, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_enridf74kzftblqd)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 2, 2026 and Aug 28, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260828.71a6399 latest | 2026-08-28 | 71a6399 | 10,229 B | A | view · diff |
| git:20260823.c767d95 | 2026-08-23 | c767d95 | 10,308 B | A | view · diff |
| git:20260811.925e30f | 2026-08-11 | 925e30f | 10,301 B | A | view · diff |
| git:20260726.3eac536 | 2026-07-26 | 3eac536 | 10,273 B | A | view · diff |
| git:20260702.cb2392a | 2026-07-02 | cb2392a | 10,059 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10229 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lugassawan/swe-workbench · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_enridf74kzftblqd GET https://markdownregistry.com/api/v1/resolve?ref=lugassawan/swe-workbench/workflow-bug-triage GET https://markdownregistry.com/api/v1/blob/a52a26b951cd1cefe291432e19969ed3f15b79d7dcf6a01ac9028de4e7d8df44
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.