issue-to-pr-resolver

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>".

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent, executable skill body: concise, copy-paste-ready commands, a clearly sequenced workflow with validation feedback loops, and clean one-level-deep referencing. No meaningful weaknesses.

Dimension	Reasoning	Score
Conciseness	The body is lean: almost every line is an executable command or a terse directive, with no explanations of concepts Claude already knows and no padding, so every token earns its place.	3 / 3
Actionability	It provides fully executable gh/git/GraphQL commands with $ARGUMENTS and $PR_NUMBER placeholders (e.g. 'gh pr create --draft', the resolveReviewThread mutation), copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	A clear five-phase sequence with an explicit feedback loop ('Repeat until all checks green and no unresolved threads', 'After pushing fixes, wait and re-check'), --watch validation checkpoints, and a max-5-iteration cap for error recovery.	3 / 3
Progressive Disclosure	Content is organized into well-labeled phases with the only external reference (AGENTS.md) kept one level deep and clearly signaled ('See AGENTS.md § Boy Scout Rule ... for the full rubric'); no nested or monolithic references.	3 / 3
	Total	12 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit what/when guidance and distinct, natural triggers. The only weakness is second-person voice ('you need to'), which the rubric penalizes on specificity.

Suggestions

Rewrite the trigger clause in third person to avoid the voice penalty, e.g. 'Use when fully implementing a GitHub issue from start to merge-ready.'

Keep the concrete action list as-is — it is the strongest part of the description.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments'), which would anchor at 3, but the second-person phrasing 'Use when you need to fully implement a GitHub issue' triggers the rubric's voice penalty reducing specificity by 1.	2 / 3
Completeness	It explicitly answers both 'what' (the end-to-end worktree→implement→PR→resolution actions) and 'when' (an explicit 'Use when...' clause plus a 'Triggers on...' list), matching the top anchor.	3 / 3
Trigger Term Quality	It provides natural trigger terms a user would actually say — 'implement issue', 'resolve issue', '/issue-to-pr-resolver <number>' — alongside 'Use when you need to fully implement a GitHub issue', giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The full issue-to-merge-ready-PR niche with a named slash-command trigger is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: homeassistant-ai/ha-mcp
Path: .claude/skills/issue-to-pr-resolver/SKILL.md
Commit: 01964cc

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.