bug-to-patch-generator
Automatically synthesizes code patches to fix identified bugs, leveraging the bug location and surrounding context. Use when a bug has been localized and the user wants an automated fix, when generating candidate patches for review, or when the user asks to fix a specific bug.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill bug-to-patch-generator93
Quality
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
82%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 solid skill description with good completeness and trigger term coverage. The explicit 'Use when...' clause with multiple scenarios is a strength. The main weakness is moderate specificity - it could benefit from listing more concrete actions (e.g., 'generates multiple patch candidates', 'validates syntax', 'preserves code style') and clearer differentiation from general code editing skills.
Suggestions
Add more specific concrete actions beyond 'synthesizes patches' - e.g., 'generates multiple candidate patches, validates syntax correctness, preserves surrounding code style'
Strengthen distinctiveness by clarifying the prerequisite (bug must already be localized) more prominently and distinguishing from general debugging or code editing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (bug fixing) and describes the action (synthesizes code patches), but lacks multiple concrete actions. 'Leveraging the bug location and surrounding context' is somewhat vague about specific capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('synthesizes code patches to fix identified bugs') and when ('Use when a bug has been localized', 'when generating candidate patches', 'when the user asks to fix a specific bug'). Has explicit 'Use when...' clause with multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'fix', 'bug', 'patch', 'automated fix', 'fix a specific bug'. These are terms users naturally use when seeking bug-fixing assistance. | 3 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to bug fixing but could overlap with general code editing or debugging skills. The focus on 'localized bugs' and 'candidate patches' helps distinguish it, but 'fix a specific bug' is broad enough to potentially conflict with other code-related skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill document that demonstrates excellent token efficiency through well-designed tables, provides fully actionable guidance with concrete code examples, and maintains clear workflow structure with explicit validation checkpoints. The preconditions table, fault classification system, and worked example combine to create a comprehensive yet concise guide for bug patching.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place—tables compress information efficiently, the worked example is tight, and there's no explanation of concepts Claude already knows. The 'Do not' section is appropriately terse. | 3 / 3 |
Actionability | Provides concrete classification tables, executable diff examples, specific validation gates, and a complete worked example with real Python code. The output format template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence (classify → draft → validate) with explicit validation gates, failure actions for each gate, and preconditions table. The 'On failure' column provides feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate cross-references to related skills (bug-localization, bug-reproduction-test-generator, behavior-preservation-checker) that are one level deep and clearly signaled in context. | 3 / 3 |
Total | 12 / 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.
- 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.