debug SKILL.md skillA
debug from yelmuratoff/agent_sync is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yelmuratoff/agent_sync/debug@git:20260728.7c60c81Pins git:20260728.7c60c81 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yelmuratoff/agent_sync
- Path
example/.ai/src/skills/debug/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260728.7c60c81, committed Jul 28, 2026
- First version recorded
- Mar 31, 2026
- Size
- 1,875 bytes
- Repository stars
- 17
- License
- GPL-3.0
Investigate and fix bugs, errors, or unexpected behavior systematically — reproduce, locate, understand the root cause, fix it, and add a regression test. Use this skill when the user reports a failure (test, runtime, build, CI), shares a stack trace or error message, says something doesn't work, asks why something is broken, or asks for a fix that requires diagnosis — even when the word "debug" is not used (e.g. "this is broken", "why is it failing", "X doesn't work").
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
# Debug
Systematically find and fix the root cause of a bug.
## Steps
1. **Reproduce** — Get the exact error message, stack trace, or steps to reproduce. Understand what happens vs. what should happen.
2. **Locate** — Narrow down where the problem is:
- Read the error message and stack trace — they usually point to the exact location.
- Search for relevant keywords (error strings, function names).
- Trace the data flow from input to the failure point.
3. **Understand** — Before fixing, understand *why* it fails:
- What assumption is violated?
- When was it introduced? (`git log`, `git blame`)
- Logic error? Data problem? Race condition? Missing edge case?
4. **Fix** — Make the smallest change that correctly addresses the root cause.
5. **Verify** — Write or update a test that catches this bug. Run the full test suite for regressions.
6. **Explain** — Briefly describe what caused it and why the fix is correct.
## Gotchas
- Don't wrap the error in try-catch to silence it — that's hiding, not fixing.
- Don't fix symptoms without understanding the cause.
- Don't make speculative changes ("maybe this will fix it") — understand first.
…Read the whole file at its exact version.
How to install
mdr add yelmuratoff/agent_sync/debug@sha256:d5ca5968d1b0ccf0The line at the top of this page pins the label git:20260728.7c60c81, 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_6hln7l5jhsys3hi7)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Mar 31, 2026 and Jul 28, 2026, about one every 60 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260728.7c60c81 latest | 2026-07-28 | 7c60c81 | 1,875 B | A | view · diff |
| git:20260425.aadd161 | 2026-04-25 | aadd161 | 1,892 B | A | view · diff |
| git:20260331.5c93cf9 | 2026-03-31 | 5c93cf9 | 1,556 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 (1875 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
yelmuratoff/agent_sync · 17 stars · license GPL-3.0 · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6hln7l5jhsys3hi7 GET https://markdownregistry.com/api/v1/resolve?ref=yelmuratoff/agent_sync/debug GET https://markdownregistry.com/api/v1/blob/d5ca5968d1b0ccf0808d3a426b038c7d0fbf40253bb2351227ceac0864818a33
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 yelmuratoff/agent_sync
Every file in yelmuratoff/agent_sync