bug-to-patch-generator

Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces. Use this skill when debugging code, fixing test failures, addressing GitHub issues, resolving runtime errors, or patching security vulnerabilities. Analyzes the bug context, identifies root causes, and generates precise code patches with explanations and validation steps.

1.33x

Quality

73%

Does it follow best practices?

Impact

100%

1.33x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bug-to-patch-generator/SKILL.md

Quality

Content

58%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.

The content offers a well-sequenced, validated workflow and concrete executable examples, but is padded with bug-category explanations and redundant code alternatives Claude already knows. More seriously, the language-specific references it points to are missing, and the body inlines material that should live in those separate files.

Suggestions

Trim or remove the explanatory prose and redundant alternative implementations (e.g. Pattern 5's multiple Counter versions) and keep only the minimal before/after fix plus a one-line rationale per pattern.

Create the four referenced files (references/python_bugs.md, javascript_bugs.md, java_bugs.md, c_cpp_bugs.md) and move the per-language and per-pattern detail into them, leaving SKILL.md as a concise overview that links one level deep.

Move the full 'Patch Presentation Format' template and 'Example Complete Patch' into a separate reference (e.g. references/patch_template.md) so the main body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body extensively explains bug categories Claude already knows (off-by-one, missing null check, race condition, memory leak, wrong exception type) with padded multi-alternative code blocks — e.g. Pattern 5 includes ~70 lines of largely redundant alternative Counter implementations — making it noticeably verbose.	2 / 5
Actionability	Provides executable, copy-paste-ready before/after code for each pattern, a structured patch template, and verification checklists that cover common cases, with only minor gaps keeping it below the fully-comprehensive level.	4 / 5
Workflow Clarity	A clear five-step workflow (Gather → Analyze → Locate → Generate → Validate) with an explicit validation step, regression checklist, and feedback loop, matching the clear-sequence-with-checkpoints anchor.	5 / 5
Progressive Disclosure	The body inlines seven full bug patterns, a complete patch template, and a full example patch that belong in separate reference files, and its four referenced files (references/python_bugs.md, javascript_bugs.md, java_bugs.md, c_cpp_bugs.md) do not exist — dead links with no actual bundle to navigate.	2 / 5
	Total	13 / 20 Passed

Description

88%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.

The description is strong: it clearly states what the skill does and when to use it, with concrete actions and natural trigger terms. Minor gaps in synonym coverage and some overlap with general debugging skills keep trigger-term quality and distinctiveness at the high-but-not-perfect level.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across several input sources — 'Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces' and 'Analyzezes the bug context, identifies root causes, and generates precise code patches with explanations and validation steps' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Generate code fixes and patches... Analyzes the bug context, identifies root causes, and generates precise code patches') and when ('Use this skill when debugging code, fixing test failures, addressing GitHub issues...'), matching the level-5 anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases users would say — 'debugging code', 'fixing test failures', 'addressing GitHub issues', 'resolving runtime errors', 'patching security vulnerabilities' — but a few common synonyms/extensions are absent, so it stops just below level 5.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct bug-to-patch niche with concrete triggers that separate it from generic debugging skills, though some minor overlap with general debugging keeps it just below the clearest-niche level.	4 / 5
	Total	18 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (734 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 4 missing	Warning
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	13 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/bug-to-patch-generator/SKILL.md
Commit: 4f38503

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