fix-issue SKILL.md skillA
fix-issue 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/fix-issue@git:20260919.72b55dcPins git:20260919.72b55dc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yelmuratoff/agent_sync
- Path
.ai/src/skills/fix-issue/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260919.72b55dc, committed Sep 19, 2026
- First version recorded
- May 17, 2026
- Size
- 3,613 bytes
- Repository stars
- 17
- License
- GPL-3.0
Investigate and fix a GitHub issue in this repo — pull the issue with `gh`, trace it to the root cause across `src/`, fix portably, and cover it with a regression test. Use this skill when the user asks to fix, resolve, or tackle a GitHub issue (by number or URL), debug a reported bug from the tracker, or work through an issue end-to-end — including phrasings like "fix #42", "tackle issue 17", "resolve this GH issue", "figure out the bug from the ticket".
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
# Fix Issue Resolve a reported GitHub issue: understand it, trace to the root cause, fix portably, and lock the fix in with a test. ## Steps 1. **Pull the issue** — `gh issue view <number>` for title, body, comments. If the user pasted a URL, extract the number from it. 2. **Reproduce** — run the failing flow against a fresh fixture (use `Project::empty()` or `Project::seeded(&[])` from `tests/common/mod.rs` so you don't contaminate the working tree). A bug you can't reproduce is a bug you can't verify fixed. 3. **Trace to the root cause** — work outward from the symptom: `src/main.rs` (command routing) → `src/cli/<cmd>.rs` (the command) → `src/render.rs` (per-tool loop) → the engine modules (`file_ops`, `yaml_subset`, `rules`, `convert`, `paths`, `backup`) → `.ai/src/tools/*.yaml`. Don't stop at the first plausible cause. 4. **Fix with the smallest correct change** — touch only the code that owns the bug. Three similar lines beat a premature abstraction. …
Read the whole file at its exact version.
How to install
mdr add yelmuratoff/agent_sync/fix-issue@sha256:6746541b2ce23ac5The line at the top of this page pins the label git:20260919.72b55dc, 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_lcguykewfn2ssgka)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 17, 2026 and Sep 19, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.72b55dc latest | 2026-09-19 | 72b55dc | 3,613 B | A | view · diff |
| git:20260919.4cf83f6 | 2026-09-19 | 4cf83f6 | 3,501 B | A | view · diff |
| git:20260728.7c60c81 | 2026-07-28 | 7c60c81 | 3,058 B | A | view · diff |
| git:20260725.ea3917b | 2026-07-25 | ea3917b | 3,102 B | A | view · diff |
| git:20260517.2521184 | 2026-05-17 | 2521184 | 2,983 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 (3613 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_lcguykewfn2ssgka GET https://markdownregistry.com/api/v1/resolve?ref=yelmuratoff/agent_sync/fix-issue GET https://markdownregistry.com/api/v1/blob/6746541b2ce23ac5e8d6c0a42b608aa2c7cde89d10db3db5db505b6f6f6fa3aa
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