ccc-systematic-debugging SKILL.md skillA
ccc-systematic-debugging from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kevinzai/commander/ccc-systematic-debugging@git:20261025.55437a6Pins git:20261025.55437a6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kevinzai/commander
- Path
commander/cowork-plugin/skills/ccc-systematic-debugging/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261025.55437a6, committed Oct 25, 2026
- First version recorded
- Jul 7, 2026
- Size
- 7,920 bytes
- Repository stars
- 6
- License
- MIT
Root-cause debugging: reproduce, hypothesize, then fix once with a failing test first. Use for a bug, a failing or flaky test, or an unknown error.
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
# /ccc-systematic-debugging — root cause before fix **CC Commander** · /ccc-systematic-debugging · a four-phase process that finds the cause, proves it, and fixes it once. ``` NO FIX WITHOUT CONFIRMED ROOT CAUSE ``` Guess-and-check fixes waste time and create new bugs; quick patches mask the real issue. Complete each phase before starting the next. ## When to use / when not to - Use for any bug, failing or flaky test, crash, wrong output, or error whose cause is not yet proven. - Use even when the issue looks simple; the process is fast for simple bugs. - Do not use for a known, already-diagnosed change (a typo the user pointed at, a requested refactor). Make that edit directly. - For investigations expected to run past ~20 turns, span several systems, or need hypothesis state held across cycles, delegate (see "Decision points"). ## What happens Start from `$ARGUMENTS` (the symptom, error text or failing test). Keep a short hypothesis log in the conversation: hypothesis, evidence, result, per cycle. ### Phase 1 — Root-cause investigation (before any fix) 1. **Read the error completely:** full stack trace, line numbers, error codes. Do not skim. …
Read the whole file at its exact version.
How to install
mdr add kevinzai/commander/ccc-systematic-debugging@sha256:15c55ac3d1267a4bThe line at the top of this page pins the label git:20261025.55437a6, 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_5t7zplytkctheu4z)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 7, 2026 and Oct 25, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.55437a6 latest | 2026-10-25 | 55437a6 | 7,920 B | A | view · diff |
| git:20261025.7eae921 | 2026-10-25 | 7eae921 | 7,891 B | A | view · diff |
| git:20261025.3b88727 | 2026-10-25 | 3b88727 | 7,916 B | A | view · diff |
| git:20261013.fbe187d | 2026-10-13 | fbe187d | 8,002 B | A | view · diff |
| git:20260707.947ab2f | 2026-07-07 | 947ab2f | 4,982 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 (7920 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
kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5t7zplytkctheu4z GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-systematic-debugging GET https://markdownregistry.com/api/v1/blob/15c55ac3d1267a4b80a815cb5b2d14d3e8d943ca1b486c57f77bdb0c88606b02
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 kevinzai/commander
Every file in kevinzai/commander