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

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

fix-bug

Étoiles2

Forks1

Mis à jour3 juillet 2026 à 23:49

Fix a bug in this repository the safe way — reproduce first, failing regression test, root cause via the maps, surgical fix, review, ledger entry. Use whenever the user reports broken, wrong, or crashing behavior.

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

kunalsuri

kunalsuri/ai-fication-kit

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

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

cold-start

kunalsuri/ai-fication-kit

Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULE_MAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.

2026-07-112

cold-start

kunalsuri/ai-fication-kit

2026-07-112

adversarial-audit

kunalsuri/ai-fication-kit

Deep, judgement-based adversarial code audit — hunts for stale cross-references, unescaped interpolation, platform gaps, generated-file ownership conflicts, and cross-module consistency rot that no mechanical check can catch. Read-only; writes a dated findings report.

2026-07-112

check-docs

kunalsuri/ai-fication-kit

Kit-maintainer diagnostic (LOCAL-ONLY, not distributed) that audits the README and docs/ for staleness against the repo's real command/skill/CLI roster, stamped tree, and cross-doc consistency. Read-only; produces a severity-ranked findings report.

2026-07-112

check-drift

kunalsuri/ai-fication-kit

Run verification and drift checks on the AI knowledge-base to identify missing documentation or stale references.

2026-07-112

create-feature-catalog

kunalsuri/ai-fication-kit

Deep-mine the source code to discover implemented features; writes ai/analysis/FEATURE_CATALOG.md.

2026-07-112

name	fix-bug
description	Fix a bug in this repository the safe way — reproduce first, failing regression test, root cause via the maps, surgical fix, review, ledger entry. Use whenever the user reports broken, wrong, or crashing behavior.

Fix a bug

The contract: no fix before a reproduction, no reproduction without a failing test, no "fixed" without the regression test green, no closing without the ledger row and the gotcha recorded.

1. Reproduce

Draft ai/lab/specs/BUGFIX_<name>.md from BUGFIX_TEMPLATE.md: symptom (observed vs expected), exact reproduction steps. Get the user's OK.

2. Prove

Turn the reproduction into a regression test and watch it fail. A bug you cannot make a test fail for is a bug you do not understand yet. The test is permanent — it outlives the fix.

3. Locate

ai/guide/MODULE_MAP.md → which modules; note Stability of every suspect.
ai/guide/FEATURE_MAP.md gotchas + ai/lab/WORKLOG.md → was this area recently touched, or is the "bug" deliberate behavior a past ADR explains?
Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.

4. Gate

Root cause in a file with Stability frozen or ? ⇒ stop and ask the human. Record their approval in the bugfix doc before proceeding.

5. Diagnose, then fix

Name the root cause in the bugfix doc — the defect, not the symptom. Then make the smallest diff that turns the regression test green. Match the license headers of neighboring files. No drive-by refactors, no layout changes, no dependency additions while "in there".

6. Verify

Run the regression test (now green), then the suites covering the touched area. Report command run · exit status · failures verbatim. Red or unrun ⇒ not fixed.

7. Review & record

Request /review-change on the diff (fresh context — not this session). Append a bugfix row to ai/lab/WORKLOG.md linking the bugfix doc and review; add the gotcha line to FEATURE_MAP so the next agent knows the trap. All [inferred] — tell the user which tags await their [verified] flip.