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

80%

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

73%Weight 40%Scale 1-5

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

A well-structured, actionable workflow with strong validation feedback loops and concrete commands. The main weaknesses are a redundant Quick Reference section and an inconsistency in branch-naming conventions.

Suggestions

Reconcile the branch-naming convention: step 2 uses 'fix-<short-description>' while step 7/Quick Reference use 'fix/issue-<issue-number>-<short-description>' — pick one and apply it consistently.

Remove or sharply compress the Quick Reference section, since it duplicates the exact commands already given in the numbered workflow steps.

Tighten filler prose such as 'Read the issue thoroughly.' and 'Take a look what is defined in composer.json...' to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-and-bullet prose, but the Quick Reference section duplicates the step commands and a few filler sentences ('Read the issue thoroughly.') could be trimmed, leaving noticeable redundancy.	3 / 5
Actionability	Concrete executable commands are provided throughout (gh issue view, git checkout -b, git commit, gh pr create, gh pr checks --watch), but inconsistent branch naming between steps (fix-<short-description> vs fix/issue-<issue-number>-...) is a minor gap.	4 / 5
Workflow Clarity	Eight clearly sequenced steps with explicit validation checkpoints and feedback loops ('Tests must pass locally before proceeding' with analyze/fix/re-run, plus CI watch with fix-and-push retry).	5 / 5
Progressive Disclosure	Well-organized with clear section headers and a self-contained single-file workflow that needs no external references, but at ~90 lines it exceeds the simple-skill threshold and no content is split out.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 trigger guidance and a clear niche. It answers both what and when and lists concrete actions, with only minor gaps in action coverage and synonym breadth.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Creates fixes on separate branches, runs tests locally, and creates PRs when tests pass') but omits CI monitoring, so minor coverage gaps remain rather than fully comprehensive.	4 / 5
Completeness	Explicitly answers both what (fix issues, branch, test, PR) and when ('Use when asked to fix, resolve, or address a GitHub issue') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user-facing verbs are present ('Use when asked to fix, resolve, or address a GitHub issue'), giving good synonym coverage, though a few colloquial variants (e.g. 'close a bug') are missing.	4 / 5
Distinctiveness Conflict Risk	The gh-CLI GitHub-issue-fixing niche has distinct triggers and minimal overlap with other skills, plus a clear prerequisites gate.	5 / 5
	Total	18 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: freekmurze/dotfiles
Path: config/claude/skills/fix-github-issue/SKILL.md
Commit: a7899fe

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.