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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

A concise, well-sequenced orchestrator body with a clear failure/escalation checkpoint. Weaker on actionability and progressive disclosure because it depends on external files that are not present in the bundle, leaving the routing unverified.

Suggestions

Add at least one inline executable snippet or concrete command so the skill is actionable even before the referenced bundle files are loaded.

Verify and include the referenced bundle files (commands/, skills/, guidelines.md) so the progressive-disclosure pointers resolve to real one-level-deep content.

Signal each reference's purpose inline (e.g., what guidelines.md contains) so navigation is unambiguous without opening every file.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no concept explanations, no padding, every line directs action. Not 2 because there is no unnecessary explanation to tighten.	3 / 3
Actionability	Guidance is concrete in routing ('read commands/{command}.md and follow it') but provides no executable code or commands itself, relying entirely on external files. Not 3 because nothing is copy-paste ready; not 1 because the routing directives are specific rather than abstract.	2 / 3
Workflow Clarity	Steps are clearly sequenced with an explicit failure checkpoint: 'If a step fails or produces unexpected output, stop and report the error... Offer to retry the failed step or escalate.' Not 2 because a validation/feedback loop is explicitly present.	3 / 3
Progressive Disclosure	The overview points to several paths (commands/, skills/, guidelines.md) but no references/, scripts/, or assets/ bundle files exist, so the referenced files cannot be verified and the structure is multi-pathed without confirmation of depth. Not 3 because the one-level-deep references are not confirmed real and well-organized; not 1 because the body itself is structured rather than a monolithic wall.	2 / 3
	Total	10 / 12 Passed

Description

92%

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-structured description: concrete actions, natural trigger terms, and an explicit 'Use when' clause. The only weakness is broad scope that risks overlapping with general coding/review skills.

Suggestions

Narrow the trigger list or add a distinguishing qualifier so this skill does not fire for routine PR review or general debugging unrelated to a structured bugfix workflow.

Consider trimming the 11-command activation list to the most essential triggers to reduce conflict with overlapping skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'analyzes error logs, traces root causes, implements fixes, and verifies with regression tests' — matching the top anchor. Not 2 because actions are specific and comprehensive rather than partial.	3 / 3
Completeness	Explicitly answers what it does AND when to use it via the 'Use when...' clause. Not 2 because the when-trigger is explicit, not merely implied.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: 'fixing bugs, debugging runtime errors or exceptions, investigating test failures or crashes'. Not 2 because it spans common variations rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	The bug-fix niche is somewhat distinct, but the broad trigger surface (debugging, test failures, PRs, plus 11 slash commands) could overlap with general coding or PR-review skills. Not 3 because of this overlap risk; not 1 because it is not generic.	2 / 3
	Total	11 / 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: amir-yogev-gh/ai-workflows
Commit: f0e2c19

Reviewed: 4 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.