fix-github-issue

Fix GitHub issues using gh CLI. Use when asked to fix, resolve, or address a GitHub issue. Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass. Requires gh CLI authenticated and repo cloned locally.

Quality

92%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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

A solid, actionable skill with a clear multi-step workflow and proper validation checkpoints for testing and CI. The main weakness is moderate verbosity — some steps contain advice Claude already knows (analyze codebase, follow code style, read the issue thoroughly), and the Quick Reference section partially duplicates the main workflow. There's also a minor inconsistency in branch naming conventions between step 2 (`fix-<description>`) and step 7 (`fix/issue-<number>-<description>`).

Suggestions

Remove obvious advice Claude already knows (e.g., 'Read the issue thoroughly', 'Make minimal, focused changes', 'Follow existing code style') to improve conciseness.

Standardize the branch naming convention — step 2 uses `fix-<description>` while step 7 uses `fix/issue-<number>-<description>`. Pick one and use it consistently.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary guidance Claude already knows (e.g., 'Read the issue thoroughly', 'Make minimal, focused changes that address the issue', 'Follow existing code style and patterns'). The 'Analyze the Codebase' step is largely obvious advice. The Quick Reference section at the end partially duplicates the workflow above.	2 / 3
Actionability	Provides concrete, executable bash commands throughout the workflow — from viewing issues, creating branches, committing, pushing, creating PRs, and monitoring CI. Commands are copy-paste ready with clear placeholders.	3 / 3
Workflow Clarity	Clear 8-step sequence with explicit validation checkpoints: tests must pass before proceeding (step 5), CI monitoring with a fix-and-retry feedback loop (step 8), and test failure recovery loop. Both destructive/important operations have proper validation gates.	3 / 3
Progressive Disclosure	For a standalone skill under 50 lines with no need for external references, the content is well-organized with clear section headers, a logical flow, and a quick reference summary. No bundle files are needed for this scope.	3 / 3
	Total	11 / 12 Passed

Description

100%

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

This is a strong skill description that clearly communicates what the skill does, when to use it, and its prerequisites. It uses concrete action verbs, includes natural trigger terms, and describes a distinct workflow that differentiates it from other skills. The description is concise yet comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: fix GitHub issues, create fixes on separate branches, run tests locally, create PRs when tests pass. Also mentions prerequisites (gh CLI authenticated, repo cloned locally).	3 / 3
Completeness	Clearly answers both 'what' (fixes GitHub issues, creates branches, runs tests, creates PRs) and 'when' (explicit 'Use when asked to fix, resolve, or address a GitHub issue'). The trigger clause is explicit and well-defined.	3 / 3
Trigger Term Quality	Includes natural trigger terms users would say: 'fix', 'resolve', 'address', 'GitHub issue', 'gh CLI', 'PR'. These cover common variations of how users would phrase requests related to this skill.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to GitHub issue fixing via gh CLI with a specific workflow (branch → test → PR). Unlikely to conflict with general coding skills or other GitHub-related skills due to the specific workflow described.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: freekmurze/dotfiles
Commit: ef5ffa0

Reviewed: 3 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.