lane-bugfix

Files (1)

• SKILL.md

SKILL.md (first lines)

# Lane: Bugfix

## Focus

- Reproduce, isolate, fix, verify.
- Address root cause, not only symptoms.
- Prevent recurrence with tests or checks.

## Starter Checklist

- [ ] Reproduction path is clear.
- [ ] Root cause identified with evidence.
- [ ] Fix is minimal and targeted.
- [ ] Verification confirms bug is resolved.
- [ ] Regression guard added or documented.

## Guardrails

- Do not broad-refactor while fixing a bug unless asked.
- If root cause is uncertain, state assumptions explicitly.

## Implementation Pattern

Evidence: 4-repo field extraction — see `.ai/MERGE_REPORT.md`.

- Fail closed and explicit on malformed input/state; never let a fix silently coerce or swallow
  an invalid case instead of surfacing it.
- Preserve existing API/wire contracts and middleware/ordering while patching; a bugfix should
  not require every caller to change unless the contract itself was the bug.
- Lock the fix to a reproducible check (a test, or a scripted repro if the project has no test
  harness for that area) before declaring it done — not just a manual one-off verification.
- Any dependency on an external script, embed, SDK, or model call needs an explicit failure
  path (fallback UI or action), not just a try/catch that logs and leaves the user stuck. This
  generalizes across domains: confirmed independently for AI model calls (`lane-ai-logic`) and
  third-party UI embeds (a booking-widget embed falling back to opening a plain link when the
  script fails to load, in `.ai/MERGE_REPORT.md`).

If the current project already has an established pattern for any of these, follow the existing
pattern instead of this default.

From JahacksV1/day-one-agent-kit, MIT.

More from JahacksV1/day-one-agent-kit