bugfix
Diagnostic and repair workflow that analyzes error logs, traces root causes, implements fixes, and verifies with regression tests. Use when fixing bugs, debugging runtime errors or exceptions, investigating test failures or crashes, or submitting bug-fix pull requests. Activated by commands: /unattended, /assess, /diagnose, /reproduce, /fix, /test, /review, /document, /pr, /feedback, /start.
94
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 what the skill does (diagnostic and repair workflow with specific steps) and when to use it (debugging scenarios with explicit triggers). It uses third person voice, includes natural trigger terms users would say, and is distinctive enough to avoid conflicts with other skills. The inclusion of slash commands adds additional specificity for activation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzes error logs', 'traces root causes', 'implements fixes', 'verifies with regression tests'. Also enumerates specific workflow commands. | 3 / 3 |
Completeness | Clearly answers both 'what' (diagnostic and repair workflow that analyzes error logs, traces root causes, implements fixes, verifies with regression tests) and 'when' (explicit 'Use when' clause covering bugs, runtime errors, test failures, crashes, and bug-fix PRs, plus command triggers). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'fixing bugs', 'debugging', 'runtime errors', 'exceptions', 'test failures', 'crashes', 'bug-fix pull requests'. Also lists explicit slash commands as triggers. These cover common variations of how users describe debugging tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to bug diagnosis and repair workflows with distinct triggers. The combination of error log analysis, root cause tracing, fix implementation, and regression testing creates a well-defined niche unlikely to conflict with general coding or testing 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 orchestrator skill that provides clear workflow sequencing, concrete examples with executable commands, and appropriate progressive disclosure to sub-skills. Its main weakness is mild redundancy between the example session, the phases list, and the /diagnose walkthrough, which could be tightened. Overall it effectively teaches Claude how to navigate a multi-phase bugfix workflow with proper validation and feedback loops.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the example session and the phases list partially overlap, and the /diagnose example is shown twice (once in Quick Start area and once as a full example). Some tightening is possible, but it doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | Provides concrete, executable commands (mkdir, rg, git blame, git log), a complete artifact template with realistic content, and clear step-by-step instructions for each phase. The root-cause.md example is copy-paste ready and demonstrates exact expected output format. | 3 / 3 |
Workflow Clarity | Multi-step workflow is clearly sequenced with numbered phases, explicit exit criteria for each phase transition, and feedback loops (test fail → return to /fix, review inadequate → return to /diagnose or /fix). The phase transitions section provides clear validation checkpoints before proceeding. | 3 / 3 |
Progressive Disclosure | SKILL.md serves as a clear overview with well-signaled one-level-deep references to skills/controller.md, skills/unattended.md, skills/{name}.md, commands/{command}.md, and guidelines.md. Content is appropriately split between the overview and referenced files, with easy navigation. | 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
- amir-yogev-gh/ai-workflows
- Commit
ab0156d
- 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.