healing-water
De la autor
Katara's healing for bugs. Use for a reported defect, a failing test, a crash, a regression, "this is broken", or "bug fix". Reproduces it on the reported surface, binary-searches the cause with runtime evidence, ships the smallest fix the evidence justifies, and proves it on the same surface.
Instalare
npx skills add tmcfarlane/team-avatar --skill healing-water -a claude-code
Se instalează în .claude/skills/healing-water/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 83
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- heal-citmcfarlane/team-avatarKatara heals a sick pipeline one wound at a time. Use for fix-ci, /fix-ci, "CI is red", "fix the failing checks", "get CI green", or a branch or PR whose checks fail. Finds the failing checks, reads the logs or external check links for the first actionable error, applies the smallest safe fix, and repeats until the checks are green.Altele★ 110
- clear-watertmcfarlane/team-avatarKatara clears the muddy water so the bottom shows. Use for no-comments, /no-comments, "remove the comments", "comment review", or before every review. Runs a fresh comment-reviewer pass over the diff, fixes the accepted findings at the root, and offers a type, test, or lint that encodes each claimed constraint so its comment can go.Testare★ 110
- purifytmcfarlane/team-avatarKatara bends the impurities out of the water and leaves it clear. Use for deslop, /deslop, "remove AI slop", "clean up this diff", or before every commit. Checks the branch diff against main and removes AI-generated code slop, such as needless comments, abnormal defensive checks, casts to any, and deep nesting, without changing behavior.Inginerie★ 110
- fixavibebuilder/claude-primeFix bugs and broken behavior when there is enough evidence to act on a repair path. Use for errors, crashes, incorrect results, API failures (500, 404, 403), CORS problems, database exceptions, broken rendering, duplicated or wrong data, off-by-one mistakes, timezone/date bugs, broken forms, config-caused runtime failures, and regressions. Trigger when the user wants the bug repaired and the conversation already contains a clear failing area, a reproducible failing test, a concrete error path, or a prior diagnosis to implement. Do NOT use for new features, pure explanation, architecture discussion, broad research, or bug reports where the main need is figuring out why the behavior happens — use diagnose for that.Testare★ 120
- root-cause-debuggingthiientv/godmodeInvestigates a bug, failing test, build error, regression, flaky behavior, performance symptom, or unexpected result by reproducing it, minimizing the case, testing ranked hypotheses, tracing the first incorrect state, and locking the root cause with a regression check. Use before proposing a fix. Not for planning a new feature or reviewing a healthy diff.Inginerie★ 99
- debuggingwjgoarxiv/litgravityFix a bug: reproduce it, test several hypotheses, isolate the cause, lock it with a failing test, then verify on the real surface.Inginerie★ 166
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te