From 1371d76904eb8974f0c557c83644ea9a8a23250a Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 6 Jul 2026 23:05:19 +0000 Subject: [PATCH] skill(bugfix-tdd): add mechanical-guardrail escalation to step 5 When a bug class repeats or has high blast radius, /learn capture alone is not enough. Add explicit guidance to identify and create a mechanical guardrail (regression test, lint rule, shared helper, docs/ai contract) so the pattern cannot recur silently. --- .agents/skills/bugfix-tdd/SKILL.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.agents/skills/bugfix-tdd/SKILL.md b/.agents/skills/bugfix-tdd/SKILL.md index eb07e65..69b65a7 100644 --- a/.agents/skills/bugfix-tdd/SKILL.md +++ b/.agents/skills/bugfix-tdd/SKILL.md @@ -62,6 +62,12 @@ class, missing guardrail, or project-specific workflow lesson. The canonical record is `docs/learnings/`; legacy files such as `BUG_PATTERNS.md` and `LESSONS_LEARNED.md` may be candidate artifacts when a project still uses them. +For repeating bug classes or fixes with high blast radius, go one step further: +identify the mechanical guardrail that would make the same class harder to write +next time — a regression test, lint rule, shared helper, ESLint restriction, or +`docs/ai` contract update. A fixed bug is fully learned only when it leaves +behind a guardrail, not just a log entry. + ### 6. Summarize Tell the user: