Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

bug-fix-prove-it

Étoiles17

Forks2

Mis à jour23 juin 2026 à 07:12

Fix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

SeemSeam

SeemSeam/agent-roles-spec

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	bug-fix-prove-it
description	Fix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.

Bug Fix Prove-It

Use this skill when the user reports a bug or asks you to fix a failing test.

Read templates/test-proof.md for the final evidence report.

Workflow

Restate the bug in observable terms.
Reproduce the failure with an existing command, manual steps, or a new test.
If reproduction is not possible, explain the proof gap before changing code.
Make the smallest fix that addresses the root cause.
Run the failing reproduction again and confirm it passes.
Run nearby regression checks when shared code was touched.
Report the before/after evidence.

Guardrails

Do not fix from intuition when a cheap reproduction is available.
Do not broaden behavior just to make the bug disappear.
Do not hide the bug with a fallback, catch-all, or default-success response.
Do not change tests to match incorrect behavior.

Output

Bug Fix Proof
- bug:
- reproduced with:
- fix:
- verified with:
- residual risk:

Plus depuis ce dépôt

même dépôt

ci-failure-fix

SeemSeam/agent-roles-spec

Fix failing tests or CI by reading logs, identifying the smallest failing surface, making a minimal change, and rerunning targeted verification. Use when given CI logs, failing commands, or broken checks.

2026-06-2317

code-context-scan

SeemSeam/agent-roles-spec

Scan relevant source, tests, commands, and existing project patterns before editing code. Use before non-trivial implementation, bug fixing, or refactoring when the right local pattern is unclear.

2026-06-2317

fallback-discipline

SeemSeam/agent-roles-spec

Control error handling, defaults, retries, compatibility paths, and fallback behavior. Use before adding catch blocks, defaults, shims, optional values, retries, or graceful degradation.

2026-06-2317

large-file-control

SeemSeam/agent-roles-spec

Prevent large-file growth and mixed-responsibility edits. Use when adding significant logic to a large file, mixed-purpose module, or file with repeated conditionals.

2026-06-2317

minimal-implementation

SeemSeam/agent-roles-spec

Implement the smallest safe repo-native code change for the requested behavior. Use for feature work, small refactors, and multi-file implementation tasks.

2026-06-2317

repo-style-following

SeemSeam/agent-roles-spec

Follow existing repository style, commands, naming, file layout, test patterns, dependency conventions, and code shape. Use when implementing in an unfamiliar repo or module.

2026-06-2317

name	bug-fix-prove-it
description	Fix bugs by reproducing the failure first, making the smallest correction, and proving the regression is covered. Use for bug reports, failing tests, and regressions.

Bug Fix Prove-It

Use this skill when the user reports a bug or asks you to fix a failing test.

Read templates/test-proof.md for the final evidence report.

Workflow

Restate the bug in observable terms.
Reproduce the failure with an existing command, manual steps, or a new test.
If reproduction is not possible, explain the proof gap before changing code.
Make the smallest fix that addresses the root cause.
Run the failing reproduction again and confirm it passes.
Run nearby regression checks when shared code was touched.
Report the before/after evidence.

Guardrails

Do not fix from intuition when a cheap reproduction is available.
Do not broaden behavior just to make the bug disappear.
Do not hide the bug with a fallback, catch-all, or default-success response.
Do not change tests to match incorrect behavior.

Output

Bug Fix Proof
- bug:
- reproduced with:
- fix:
- verified with:
- residual risk: