issue-to-pr-resolver SKILL.md skillA
issue-to-pr-resolver from homeassistant-ai/ha-mcp is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add homeassistant-ai/ha-mcp/issue-to-pr-resolver@git:20260926.4e60907Pins git:20260926.4e60907 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- homeassistant-ai/ha-mcp
- Path
.claude/skills/issue-to-pr-resolver/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260926.4e60907, committed Sep 26, 2026
- First version recorded
- May 6, 2026
- Size
- 4,633 bytes
- Repository stars
- 5,167
- License
- MIT
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve issue", "/issue-to-pr-resolver <number>".
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
# Issue-to-PR Resolver Implement GitHub issue #$ARGUMENTS in `homeassistant-ai/ha-mcp` end-to-end. ## Phase 1: Setup **Read the issue:** ```bash gh issue view "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --json title,body,labels,comments,author ``` **Create a worktree from repo root:** ```bash cd "$(git rev-parse --show-toplevel)" git checkout master && git pull origin master git worktree add "worktree/issue-$ARGUMENTS" -b "feature/issue-$ARGUMENTS" git -C "worktree/issue-$ARGUMENTS" submodule update --init --recursive cd "worktree/issue-$ARGUMENTS" ``` ## Phase 2: Implement - Analyze codebase structure and patterns before writing code - Follow project conventions (see `AGENTS.md` for patterns, naming, error handling) - Write tests — all new MCP tools in `src/ha_mcp/tools/` need E2E tests - Make atomic, well-described commits using conventional commit prefixes **Philosophy:** Work autonomously. Don't ask about every small decision. Fix unrelated test failures encountered. Document all choices for the final summary. If a non-obvious choice has significant consequences, present the available options to the user and let them choose. ## Phase 3: Create PR …
Read the whole file at its exact version.
How to install
mdr add homeassistant-ai/ha-mcp/issue-to-pr-resolver@sha256:0d6f96689ac80332The line at the top of this page pins the label git:20260926.4e60907, 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_nb6rbftyhpa4p4fz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 6, 2026 and Sep 26, 2026, about one every 48 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.4e60907 latest | 2026-09-26 | 4e60907 | 4,633 B | A | view · diff |
| git:20260831.9fc3309 | 2026-08-31 | 9fc3309 | 4,315 B | A | view · diff |
| git:20260518.4e02d30 | 2026-05-18 | 4e02d30 | 4,330 B | A | view · diff |
| git:20260506.0c8cd0d | 2026-05-06 | 0c8cd0d | 4,360 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 (4633 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
homeassistant-ai/ha-mcp · 5,167 stars · license MIT · pushed 2026-10-21 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_nb6rbftyhpa4p4fz GET https://markdownregistry.com/api/v1/resolve?ref=homeassistant-ai/ha-mcp/issue-to-pr-resolver GET https://markdownregistry.com/api/v1/blob/0d6f96689ac803326ce5ba9021199d9f6055e39a3634dc70dfa26af41c6f3929
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.