fix-issue SKILL.md skillA
fix-issue from gufranco/claude-engineering-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gufranco/claude-engineering-rules/fix-issue@git:20261028.2d1ff0cPins git:20261028.2d1ff0c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gufranco/claude-engineering-rules
- Path
skills/fix-issue/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.2d1ff0c, committed Oct 28, 2026
- First version recorded
- Oct 12, 2026
- Size
- 8,323 bytes
- Repository stars
- 3
- License
- MIT
Fix a GitHub issue by number. Fetches the issue, analyzes requirements, searches the codebase, implements the fix with tests, and commits referencing the issue. Use when user says "fix issue #N", "fix #N", "resolve issue N", "close issue N", when /morning works an assigned issue, or wants to implement a fix for a specific GitHub issue. For general debugging without an issue, use /investigate; for code review, use /review; for feature planning, use /plan.
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
## Overview End-to-end workflow for resolving a GitHub issue: from reading the issue to committing a tested fix. ## When to Use Run with an issue number when the issue itself holds the requirements. Pass `--dry-run` to get the proposed approach, affected files, and test plan before any code is written. ### Arguments - `<number>` is required: the GitHub issue number to fix. - `--dry-run`: analyze and propose a fix without implementing. ## Process ### Phase 1: Understand 1. **Fetch the issue into a file.** Run: ```bash issue_file="$(mktemp -t issue-XXXXXX).json" GH_TOKEN=$(gh auth token --user <account>) gh issue view <number> --json title,body,labels,assignees,comments > "$issue_file" ``` Determine the account from the git remote URL using the mapping in [`standards/github-accounts.md`](../../standards/github-accounts.md). Read `$issue_file` with the Read tool. …
Read the whole file at its exact version.
How to install
mdr add gufranco/claude-engineering-rules/fix-issue@sha256:0bb2a68a5573467eThe line at the top of this page pins the label git:20261028.2d1ff0c, 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_rhqxpmtxbka3pqqi)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 12, 2026 and Oct 28, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.2d1ff0c latest | 2026-10-28 | 2d1ff0c | 8,323 B | A | view · diff |
| git:20261028.fa538f0 | 2026-10-28 | fa538f0 | 8,329 B | A | view · diff |
| git:20261013.02cb8cd | 2026-10-13 | 02cb8cd | 7,853 B | A | view · diff |
| git:20261013.b817909 | 2026-10-13 | b817909 | 7,724 B | A | view · diff |
| git:20261012.84ebb18 | 2026-10-12 | 84ebb18 | 7,662 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 (8323 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
gufranco/claude-engineering-rules · 3 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rhqxpmtxbka3pqqi GET https://markdownregistry.com/api/v1/resolve?ref=gufranco/claude-engineering-rules/fix-issue GET https://markdownregistry.com/api/v1/blob/0bb2a68a5573467e0b9d6d2fed64ba2543b512e0c92e16275bce1c81bd6b3fa2
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 gufranco/claude-engineering-rules
Every file in gufranco/claude-engineering-rules