fix-issue

Use when working on a GitHub issue - fetches issue details, analyzes codebase, implements fix following project methodology

Quality

82%

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

81%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, highly actionable fix-issue workflow with strong validation checkpoints and checklists. Its main weakness is conciseness: the diagram and Quick Reference table restate content already present in the step sections.

Suggestions

Remove or shrink the graphviz 'fix_flow' diagram: it restates the Step 1–8 sequence already conveyed by the section headers, saving ~20 lines with no loss of clarity.

Drop the Quick Reference table (or reduce it to non-obvious commands only) since every command it lists already appears in the relevant step.

Tighten 'following project methodology' phrasing and the prose intros in the Contributor Credit / Community Communication sections to pure directives.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of generic-concept padding, but the graphviz 'fix_flow' diagram (~22 lines) duplicates the numbered Step 1–8 headers and the Quick Reference table repeats commands already shown in their steps, which is noticeable redundancy that could be trimmed.	3 / 5
Actionability	Abundant copy-paste-ready commands (gh issue view, git checkout -b, terraform fmt/init/validate/plan) and a heredoc commit-message template cover the common cases fully; placeholders like <number> are appropriate templating rather than gaps.	5 / 5
Workflow Clarity	An 8-step numbered sequence with explicit validation checkpoints (Step 3 verify-before-fixing, Step 5 mandatory plan mode, Step 7 test checklist), feedback loops, and checklists; destructive-operation validation is present so the cap does not apply.	5 / 5
Progressive Disclosure	Sections, tables, and headers give clear structure and references to repo files (CHANGELOG.md, MIGRATION.md) and sibling skills (test-changes, review-pr) are clearly signaled; no bundle files exist to navigate, and a few long inline sections (Contributor Credit, Community Communication) could arguably be split, keeping it at 4.	4 / 5
	Total	17 / 20 Passed

Description

83%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, third-person description that pairs an explicit 'Use when…' trigger with three concrete actions. It is held below the top tier only by mild filler ('following project methodology') and a few missing trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the GitHub-issue domain and three concrete actions ('fetches issue details, analyzes codebase, implements fix'), but 'following project methodology' is mild filler and coverage omits testing/committing/PR creation, so it sits at anchor 4 rather than 5.	4 / 5
Completeness	Explicitly answers both 'when' ('Use when working on a GitHub issue') and 'what' ('fetches issue details, analyzes codebase, implements fix') with concrete trigger phrasing, matching the anchor-5 example.	5 / 5
Trigger Term Quality	'working on a GitHub issue' is exactly the natural phrase a user would say and is centrally placed as the trigger; a few common synonyms (bug, bug report, issue tracker) are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'GitHub issue' fix niche is distinct from most skills, but it shares commit/PR territory with the sibling 'review-pr' skill referenced in the body, creating minor overlap risk rather than minimal.	4 / 5
	Total	17 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: mysticaltech/terraform-hcloud-kube-hetzner
Path: .claude/skills/fix-issue/SKILL.md
Commit: bb1622c

Reviewed: 1 day 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.