Skip to content
Skills Library
Programming · Building & coding

program-repair

/program-repair

Localise, write several patches, and keep the one that holds. Use when the task involves: automated program repair, fault localization, majority vote patch, repair, localize, patch generation.

Licence
Apache-2.0
Last repository change
12.11.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Localise, write several patches, and keep the one that holds. Use when the task involves: automated program repair, fault localization, majority vote patch, repair, localize, patch generation.

Original author description

Localise, write several patches, and keep the one that holds. Use when the task involves: automated program repair, fault localization, majority vote patch, repair, localize, patch generation.

How it works

SKILL.md has no level-two headings · 14 lines, 158 words

SKILL.md preview
---
name: program-repair
description: "Localise, write several patches, and keep the one that holds. Use when the task involves: automated program repair, fault localization, majority vote patch, repair, localize, patch generation."
user-invocable: false
metadata:
  short-description: "Localise, write several patches, and keep the one that holds."
---

# program-repair

Repair a reproducible failure with bounded candidate evaluation.

1. Identify the failing test or executable acceptance condition. If there is none, establish a reproducer before generating patches.
2. Use the traceback and `find_definition`, `find_usages` and `blast_radius` to localize the cause and affected contracts.
3. Set the candidate count, time limit and resource budget. Prefer one minimal fix; use isolated alternatives when the cause or design remains contested.
4. Compile/type-check and run the reproducer for each candidate. Discard candidates that do not fix the target behavior.
5. Run the relevant regression tests and `scan` for changes to security-sensitive surfaces. Use `review` to inspect arguable logic and examine every material finding.
6. Keep the smallest supported repair. If no candidate works within the bounds, report the experiments and unresolved cause rather than declaring success.

Return a reviewable patch and measured before/after evidence. Do not select correctness by model majority vote, merge automatically, or launch paid work without authorization.

Versions

The database has no other skills named program-repair.

Database snapshot: 13.11.2026 · package version f6757986abe0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 96recipe-vote-schedule
    Use when running the household recipe-vote program.
  • 100reasoning-semiformally
    Apply semi-formal certificate reasoning to code analysis — patch verification, fault localization, patch equivalence. Use when reviewing patches, hunting bugs across scopes, comparing fixes, or when code reasoning requires tracing execution across files/modules. Triggers on code…
  • 100assess-patch-risk
    Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This…
  • 98assess-patch-risk
    Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.