code-repair-generation-combo

Automatically repair buggy code and generate comprehensive tests for Python, Java, and C++ programs. Use when users need to fix logic errors or runtime errors in functions, modules, or repositories. Accepts specifications via natural language descriptions, existing test cases, or input/output examples. Generates corrected code, creates or updates tests to verify correctness and prevent regressions, and produces a detailed report explaining the bug, fix, and testing strategy. Triggers on requests like "fix this bug", "repair this code", "debug this function", or "this code is broken".

1.14x

Quality

86%

Does it follow best practices?

Impact

95%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

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

A well-structured workflow skill with clear sequencing, explicit validation/feedback loops, and properly split one-level-deep references to real bundle files. It loses points mainly on conciseness for re-explaining basic programming concepts Claude already knows.

Suggestions

Trim or remove the bug-type definitions (logic vs runtime error examples) and generic process pointers like 'Trace the logic' and 'Preserve code style' that Claude already knows, keeping only skill-specific guidance.

Consider condensing the three 'Example Usage' blocks into one representative example, or move them into a reference file, to reduce token overhead.

Add at least one concrete before/after fix code snippet to the 'Fix the Code' step so the repairing guidance is as executable as the testing guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but several sections explain concepts Claude already knows — bug-type definitions ('off-by-one, wrong operator', 'null pointer, array out of bounds'), generic process pointers ('Trace the logic', 'Preserve code style'), and three full worked examples that could be tightened.	3 / 5
Actionability	Provides concrete executable commands ('pytest test_file.py -v', 'mvn test', 'ctest') and real reference/template file paths, but the code-fixing steps themselves stay abstract ('Apply minimal changes', 'Use Edit tool') with no fix code examples.	4 / 5
Workflow Clarity	A clearly sequenced six-step process with an explicit validation checkpoint and feedback loop ('If tests fail, revisit the fix') plus a test-case checklist (normal/edge/error/regression), matching the top anchor for explicit validation and error-recovery loops.	5 / 5
Progressive Disclosure	The body is a concise overview with well-signaled one-level-deep references to verified bundle files (references/{python,java,cpp}-testing.md, assets/bug-fix-report-template.md), with testing patterns and the report template appropriately split into separate files.	5 / 5
	Total	17 / 20 Passed

Description

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

A strong, concrete description that explicitly states both what the skill does and when to use it, with natural trigger phrases and broad language coverage. Its only weakness is that combining code repair with test generation invites minor overlap with standalone debugging or testing skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the full lifecycle — 'repair buggy code', 'generate comprehensive tests', 'creates or updates tests', 'produces a detailed report' — plus three input-spec forms and three languages, giving comprehensive coverage rather than just several actions.	5 / 5
Completeness	Clearly answers 'what' (repair, test, report across Python/Java/C++) and 'when' with an explicit 'Use when users need to fix logic errors or runtime errors' clause plus concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Explicit natural user phrases ('fix this bug', 'repair this code', 'debug this function', 'this code is broken') plus the synonyms fix/repair/debug/broken cover the ways a user would naturally request this skill.	5 / 5
Distinctiveness Conflict Risk	Triggers like 'debug this function' are distinct but the skill combines two common capabilities (debugging + test generation), creating minor overlap risk with closely related single-purpose debugging or testing skills rather than minimal conflict risk.	4 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Path: skills/code-repair-generation-combo/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.