Validate Fix
Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says "is this fixed?", or before closing an investigation.
Install
npx skills add danielvm-git/bigpowers --skill validate-fixgit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/validate-fix ~/.claude/skills/validate-fixPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Validate Fix > **HARD GATE** — Fix must not regress. Run full test suite and manual UAT before declaring success. Prove the fix works. "I think it works" is not evidence. Run the suite, show the output, then harden against recurrence. > **Two-commit red/green policy (e45s08)** — Bug fixes follow the same two-commit discipline as `develop-tdd`: first commit adds/adjusts the failing test (`test(<scope>): …`), second commit applies the fix (`fix(<scope>): …`). Do not squash RED and GREEN before review. ## Checklist ### 1. Re-run the originally failing test ```bash # Run the specific test that captured the bug <test command for the failing test> ``` - [ ] Previously failing test now passes ### 2. Run the full test suite ```bash # Run all tests — no filtering <full test command from CLAUDE.md> ``` - [ ] All tests pass (zero regressions) ### 3. Type check ```bash <typecheck command> ``` - [ ] No type errors introduced ### 4. Lint ```bash <lint command> ``` - [ ] No lint violations introduced ### 5. Harden against recurrence For every bug fixed, add at least one prevention layer: | Mechanism | When to use | |-----------|-------------| | Type guard | Input could be the wrong shape | | Schema validation (Zod, Pydantic, etc.) | External data crossing a boundary | | Invariant assertion | Internal state that must always hold | | Lint rule | Pattern that's easy to repeat by mistake | | Environment check at startup | Missing config causes silent failure |
Details
- Skill name
validate-fix- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/validate-fix/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Validate Fix skill do?
Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says "is this fixed?", or before closing an investigation.
How do I install the Validate Fix skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill validate-fix. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Validate Fix popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Verify Work
292danielvm-git/bigpowers
Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-by-step manual verification, gaps-closure loop. Use after execute-plan or develop-tdd, before audit-code.
Terse Mode
292danielvm-git/bigpowers
Fallback ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use ONLY when context is critically long and compressing output is necessary to continue. Not a strategy — token discipline comes from code shape (small functions, unique names, headless tests), not terser prompts. Use when user says "caveman mode", "terse mode", "less tokens", "be brief", or invokes /terse-mode.
Browserstack
100adriannoes/awesome-agentic-ai
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.