fixing-bugs SKILL.md skillA
fixing-bugs from cristhianzl/claude-skills-czl is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cristhianzl/claude-skills-czl/fixing-bugs@git:20260806.29b92b9Pins git:20260806.29b92b9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cristhianzl/claude-skills-czl
- Path
configs/agnostic/skills/fixing-bugs/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260806.29b92b9, committed Aug 6, 2026
- First version recorded
- Jun 19, 2026
- Size
- 13,241 bytes
- Repository stars
- 5
- License
- MIT
Fix a bug using strict TDD — UNDERSTAND → REPRODUCE (RED) → VERIFY RED → FIX → VERIFY GREEN → VALIDATE → REFACTOR. Use when the user reports a bug, asks to fix something, mentions a Sentry/error/regression, or pastes a stack trace. Bugs require a failing test that proves the bug existed before any code change. For building new features use developing-features-tdd; for non-TDD code work use developing-features.
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
# Fixing Bugs Never fix a bug before proving it exists with a failing test. The fix is only valid if a test transitions from RED (failing) to GREEN (passing). ## Read first (always) List `learnings/` and read every file relevant to the current bug. Project-specific test conventions, framework quirks, recurring bug patterns, or hot zones live there and override the defaults in this SKILL.md. If a learning conflicts with this file, **the learning wins** — mention it to the user. ## Tradeoff — when to apply, when to lighten up Apply the full cycle for **any defect in production code** the user is reporting (Sentry alert, support ticket, "this broke", regression). The discipline pays off because the test becomes a permanent sentinel against the same bug returning. Lighten the formality only when fixing a typo, a build script, or a one-off script the user explicitly labels as throwaway. Even then, run the test suite afterwards. ## The cycle (strict order) ``` 1. UNDERSTAND → Read the bug report; identify expected vs actual; locate the OS/platform 2. REPRODUCE → Write a failing test that triggers the EXACT error path …
Read the whole file at its exact version.
How to install
mdr add cristhianzl/claude-skills-czl/fixing-bugs@sha256:7e96a383e33ff966The line at the top of this page pins the label git:20260806.29b92b9, 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_tjvsky3drgc23o4y)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 19, 2026 and Aug 6, 2026, about one every 48 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260806.29b92b9 latest | 2026-08-06 | 29b92b9 | 13,241 B | A | view · diff |
| git:20260619.c43368b | 2026-06-19 | c43368b | 13,082 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 (13241 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
cristhianzl/claude-skills-czl · 5 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tjvsky3drgc23o4y GET https://markdownregistry.com/api/v1/resolve?ref=cristhianzl/claude-skills-czl/fixing-bugs GET https://markdownregistry.com/api/v1/blob/7e96a383e33ff9660c273643ce1bd49610cb70592f62c2621b366e54c7d28317
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 cristhianzl/claude-skills-czl
Every file in cristhianzl/claude-skills-czl