Repairs build, lint, and type-check failures with minimal verified changes.
npx skills add https://github.com/kieranpotts/skills --skill fix-kieranpotts
Please help me install this Agent Skill. Skill: fix Source: https://github.com/kieranpotts/skills/tree/main/skills/fix Command: npx skills add https://github.com/kieranpotts/skills --skill fix-kieranpotts
--fix flags and codemods before manual edits. - Diagnosis handover support: Acts on a confirmed causal chain and failing regression test from a prior diagnosis, verifying the test goes green with the fix and red again when reverted. - Guardrails against scope creep: Forbids refactors, renames, weakened tests, and unexplained suppressions riding along in the repair diff. - Use Case: After CI reports eslint failures on a pull request, invoke the Skill to run the linter, apply autofixes, manually resolve remaining violations at their reported locations, and confirm every project check passes before committing. ## Quick Start Fix the lint errors reported in the latest CI run and verify all project checks pass afterward.High-intent search queries and answers about installing and using this skill.
Run the linter with its autofix flag first, such as eslint --fix, then re-run to see what remains. Fix each remaining violation manually at the exact rule and location the tool reports, and re-run the check to confirm zero violations.
Re-run the exact command that originally failed and confirm it exits zero. If a regression test was handed over, watch it pass with the change applied, then revert the change and confirm it fails again, proving the test exercises the fix.
Suppress only when the rule is genuinely wrong for that specific case, and always name the rule plus the reason inline, such as eslint-disable-next-line no-explicit-any with a justification. Unexplained suppressions hide signal from future readers.
Stop rather than guessing repeatedly. A repair workflow only applies when a tool or completed diagnosis has established the cause; otherwise hand the work to a systematic diagnosis process that forms and tests hypotheses first.
Narrowing a shared type or bumping a dependency can cascade errors across call sites. Work outward from the original error since downstream failures usually resolve once the upstream cause does, and treat large cascades as a maintenance sweep.
AndurilCodeDiagnose unexplained software failures through an evidence-first root-cause workflow.
0xharryriddlePrepare pull requests with atomic commits, conventional messages, and CI checks.
jangtrinhRun linters and type checkers on Node.js and Python projects.
jeremybrasherQuestions the shared premise behind repeatedly failed fixes using an actor imbalance census.