diagnosing-bugs SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 5 indexed copies. Same content hash, so the same checks give both the same grade.

diagnosing-bugs from j-star-films-studios/vibecode-protocol-suite is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add j-star-films-studios/vibecode-protocol-suite/diagnosing-bugs@git:20260821.1b830a3

Pins git:20260821.1b830a3 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

j-star-films-studios/vibecode-protocol-suite

Path

assets/.agent/skills/code-intelligence/diagnosing-bugs/SKILL.md

Versions recorded

1

Latest version

git:20260821.1b830a3, committed Aug 21, 2026

Size

8,529 bytes

Repository stars

26

License

ISC

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

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

# Diagnosing Bugs

A discipline for hard bugs. Skip phases only when explicitly justified.

When exploring the codebase, read `CONTEXT.md` (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.

## Redact

This skill has you show commands, outputs and captured artifacts. **Redact every secret first**: write `<REDACTED>` in its place. Build loops against env vars, so the credential stays in the environment rather than in what you show. Captured artifacts carry auth headers: quote only the lines that carry the signal.

If the redacted output is not enough to diagnose the bug, say so and ask the user.

## Phase 1: Build a feedback loop

**This is the skill.** Everything else is mechanical. If you have a **tight** pass/fail signal for the bug (one that goes red on _this_ bug), you will find the cause; bisection, hypothesis-testing, and instrumentation all just consume it. If you don't have one, no amount of staring at code will save you.

Spend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.**

### Ways to construct one, in roughly this order
…

Read the whole file at its exact version.

How to install

mdr add j-star-films-studios/vibecode-protocol-suite/diagnosing-bugs@sha256:77f3cf31bc99b2f4

[![mdr](https://markdownregistry.com/badge/art_tuxgs45p5yt4zesh.svg)](https://markdownregistry.com/a/art_tuxgs45p5yt4zesh)

Versions

The registry has recorded 1 version of this file, committed on Aug 21, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_tuxgs45p5yt4zesh
GET https://markdownregistry.com/api/v1/resolve?ref=j-star-films-studios/vibecode-protocol-suite/diagnosing-bugs
GET https://markdownregistry.com/api/v1/blob/77f3cf31bc99b2f49af943222526531fcc9fc41d047626d3640e875e85af3e84

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.

More from j-star-films-studios/vibecode-protocol-suite

Every file in j-star-films-studios/vibecode-protocol-suite

Other files named diagnosing-bugs

Browse by kind, by grade A, or by owner.