fix-issue

Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Use when asked to fix an issue: "fix issue 1234", "resolve #500", "create a PR for issue 200".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

A well-structured orchestrator skill that delegates to composable sub-skills through a clear numbered workflow with explicit decision branches, executable commands, and a re-review feedback loop. It is concise, actionable, and appropriately self-contained with no nested references.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: each step is a sentence or two invoking a sub-skill with no concept explanation or padding, and every line earns its place.	3 / 3
Actionability	Provides copy-paste-ready `gh issue close` and `gh issue comment` commands plus explicit sub-skill invocations (/triage-issue, /research, /write, /review-changes, /create-pr), giving fully executable guidance.	3 / 3
Workflow Clarity	A clearly numbered 1–8 sequence with explicit decision branches in step 2 and a re-review feedback loop in step 5 ("fix them and re-review until clean"), giving explicit checkpoints and error recovery.	3 / 3
Progressive Disclosure	A self-contained single-file orchestrator with well-organized sections and one-level sub-skill references; no bundle files exist and there are no deeply nested references, so structure is appropriate for its scope.	3 / 3
	Total	12 / 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.

A strong, well-scoped description that names concrete end-to-end actions, supplies natural user trigger phrases, and clearly states when to invoke it. Third-person voice is maintained and there is no fluff or over-claiming.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "triage, research, write the fix, review, and create a PR" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (fix a single GitHub issue end-to-end with named steps) and when ("Use when asked to fix an issue" with example triggers).	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would actually say ("fix issue 1234", "resolve #500", "create a PR for issue 200"), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	"Fix a single GitHub issue end-to-end" scoped to an issue-number argument is a clear niche with distinct triggers, unlikely to collide with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: docker/docs
Commit: 67d0999

Reviewed: about 12 hours 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.