gh-issue-fix-flow
End-to-end GitHub issue fix workflow using gh, local code changes, builds/tests, and git push. Use when asked to take an issue number, inspect the issue via gh, implement a fix, run XcodeBuildMCP builds/tests, commit with a closing message, and push.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 articulates a specific end-to-end workflow with concrete actions and explicit trigger conditions. It uses third person voice correctly, includes natural developer terminology, and the combination of GitHub CLI, XcodeBuild, and git operations makes it highly distinctive. The 'Use when...' clause provides clear guidance on when Claude should select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'inspect the issue via gh', 'implement a fix', 'run XcodeBuildMCP builds/tests', 'commit with a closing message', and 'push'. These are clear, actionable steps in a workflow. | 3 / 3 |
Completeness | Clearly answers both what ('End-to-end GitHub issue fix workflow using gh, local code changes, builds/tests, and git push') AND when ('Use when asked to take an issue number, inspect the issue via gh, implement a fix...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'issue number', 'gh', 'fix', 'builds/tests', 'git push', 'commit', 'GitHub issue'. Good coverage of terms a developer would naturally use when requesting this workflow. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tooling references (gh CLI, XcodeBuildMCP) and a complete workflow scope. The combination of GitHub issues + Xcode builds + git operations creates a clear niche unlikely to conflict with generic git or code skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured workflow skill that efficiently guides Claude through a complete GitHub issue fix process. The content is appropriately concise and has clear validation checkpoints. The main weakness is that commands are referenced but not shown with complete executable syntax or example outputs.
Suggestions
Add a complete example showing the full gh issue view command with sample output format
Include an example commit message showing the exact 'closes #<issue>' format expected
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Each step is direct and assumes competence with tools like gh, git, and rg. | 3 / 3 |
Actionability | Provides specific commands (gh issue view, rg -n, git status --short) but lacks complete executable examples. Commands are mentioned but not shown with full syntax or expected outputs. | 2 / 3 |
Workflow Clarity | Clear 6-step sequence with logical progression from intake to reporting. Includes validation checkpoints (build/test before commit, check for unrelated changes) and explicit error handling guidance (macOS test fallback to iOS simulator). | 3 / 3 |
Progressive Disclosure | For a workflow skill of this scope (~50 lines), the content is well-organized with clear section headers. No external references needed; the single-file structure is appropriate for this procedural guide. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%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
- Dimillian/Skills
- Commit
527d603
- Reviewed
Table of Contents
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.