Agent skill

Validate Fix

by danielvm-git in danielvm-git/bigpowers

Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence.

MITAuto-check passedDevelopment

Install Validate Fix

skills CLI
$ npx skills add danielvm-git/bigpowers --skill validate-fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install danielvm-git/bigpowers validate-fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/validate-fix .claude/skills/validate-fix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
validate-fix
GitHub stars
256
Token cost
~1.1k tokens
SKILL.md length
438 words
Files
2
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence.

  • Works in 7 steps: Re-run the originally failing test → Run the full test suite → Type check → …
  • Says is this fixed?
  • SKILL.md covers Checklist, Rules and Verify
  • Calls bash

What it does

Validate Fix is an agent skill from danielvm-git/bigpowers. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `REFERENCE-generalize-fix.md`).

It sits in Development, covering Failing and flaky tests, Debugging and Linting and formatting. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.

When your agent uses it

  • Says is this fixed?
  • Before closing an investigation

Example prompts

  • “is this fixed?”
  • “/validate-fix”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Re-run the originally failing test
  2. Run the full test suite
  3. Type check
  4. Lint
  5. Harden against recurrence
  6. Update the bug file and registry.yaml
  7. Behavioral Proof (HARD GATE)

What it can do on your machine

Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Validate Fix loads about 1.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 438 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 438 words, ~1,061 tokens.

Download SKILL.mdSave it as .claude/skills/validate-fix/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
validate-fix
description
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.
model
haiku
effort
standard

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:

MechanismWhen to use
Type guardInput could be the wrong shape
Schema validation (Zod, Pydantic, etc.)External data crossing a boundary
Invariant assertionInternal state that must always hold
Lint rulePattern that's easy to repeat by mistake
Environment check at startupMissing config causes silent failure
  • At least one hardening mechanism added
  • Hardening mechanism is tested
5b. Generalize-fix (HARD GATE — e80s04 / GH #98)

Sweep the defect class across the codebase after local hardening — see REFERENCE-generalize-fix.md.

  • Defect class documented (not just the one-line root cause)
  • Grep sweep run and match_count recorded
  • verify-generalize-sweep.sh passes on the artifact
6. Update the bug file and registry.yaml

Find the most recent specs/bugs/BUG-*.md file and append the resolution:

markdown
## Resolution

**Fixed:** [date]
**Root cause confirmed:** [one sentence]
**Fix applied:** [what was changed]
**Hardening added:** [type guard / schema / assertion / lint rule]
**Evidence:** all tests pass (`<verify command>`)
**Commit:** `fix(<scope>): <description>`

Also update the corresponding row in specs/bugs/registry.yaml: set status to fixed, fill in files_changed, approach, risk_level, commit_message, and any other resolution fields.

  • specs/bugs/BUG-*.md updated with resolution
  • specs/bugs/registry.yaml row updated with resolution fields
Show full SKILL.md (169 more words)Show less
7. Behavioral Proof (HARD GATE)

Mechanical verification (tests passing) is only half the fix. You must prove behavioral correctness.

  • Manually demonstrate the fixed behavior (e.g., via run_shell_command or web_fetch)
  • Compare the output/state against the "Expected Behavior" in the bug file
  • Show the user evidence of the behavior, not just the test logs

Rules

  • Loop until behavioral correctness is verified: if any checklist item fails, or if the behavior is still incorrect despite passing tests, return to step 1 and run all checks again from the top — do not declare done until every item is green and the behavior is proven correct in a single run.
  • Never use @ts-ignore, as any, or // eslint-disable to "fix" a bug — these suppress the symptom without fixing the root cause
  • Never mark the task done if any test is still failing
  • The verify command from specs/bugs/BUG-*.md or the active epic task verify field must pass

Suggest next skill: audit-code → commit-message.

Verify

→ verify: grep -q 'generalize-fix' skills/validate-fix/SKILL.md && test -x scripts/verify-generalize-sweep.sh && bash scripts/verify-generalize-sweep.sh --self-test && echo OK

© danielvm-git, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/validate-fix of danielvm-git/bigpowers.

  • SKILL.md
  • REFERENCE-generalize-fix.md

Open the folder on GitHubat commit 812d57a

Compare with similar skills

Validate Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Validate Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Validate Fix this skilldanielvm-git/bigpowers256—~1.1kAutomated safety check: PassMIT
Authoring CI WorkflowsPostHog/posthog-foss721—~11kAutomated safety check: PassMIT
React Router Bug Fix Workflowremix-run/react-router57k—~1.3kAutomated safety check: PassMIT
Adk Setupgoogle/adk-python22k—~993Automated safety check: NotesApache-2.0
Runtime DebugOpenHikmah/openhikmah-web181—~618Automated safety check: PassGPL-3.0
Root Cause Debuggingjsmastery-pro/skills1.4k—~1.8kAutomated safety check: NotesMIT

Similar skills

  • Authoring CI Workflows

    PostHog/posthog-foss

    Official

    A skill your agent uses when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action…

    721 GitHub stars~11k tokensUpdated today
    DevelopmentAuto-check passed
  • React Router Bug Fix Workflow

    remix-run/react-router

    Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.

    57k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Adk Setup

    google/adk-python

    Official

    Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…

    22k GitHub stars~993 tokensUpdated today
    DevelopmentAuto-check: notes
  • Runtime Debug

    OpenHikmah/openhikmah-web

    Debug and verification workflow for runtime-bundle and module-resolution regressions.

    181 GitHub stars~618 tokensUpdated today
    DevelopmentAuto-check passed
  • Root Cause Debugging

    jsmastery-pro/skills

    Runs a reproduce, localize, hypothesize, test, fix and verify loop to find a bug's root cause, applies the minimal fix and hands off a regression test.

    1.4k GitHub stars~1.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes
  • Fix

    BUZZARDGTA/Session-Sniffer

    Diagnose and fix Session Sniffer bugs, errors, tracebacks, logs, lint failures, static-analysis findings, test failures, and IDE-reported problems.

    104 GitHub stars~2.7k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from danielvm-git/bigpowers

All 39 skills in this repo
  • Extract Design

    danielvm-git/bigpowers

    Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose.

    256 GitHub stars~1k tokensUpdated 16 days ago
    Auto-check passed
  • Align Grid

    danielvm-git/bigpowers

    Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one.

    256 GitHub stars~3k tokensUpdated 16 days ago
    Auto-check passed
  • Assess Impact

    danielvm-git/bigpowers

    Analyze the blast radius of a proposed change before any code is written.

    256 GitHub stars~766 tokensUpdated 16 days ago
    Auto-check passed
  • Audit Code

    danielvm-git/bigpowers

    Self-review checklist for the coding agent to run before dispatching a reviewer.

    256 GitHub stars~1.6k tokensUpdated 16 days ago
    Auto-check: notes
  • Audit Plan

    danielvm-git/bigpowers

    Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins.

    256 GitHub stars~880 tokensUpdated 16 days ago
    Auto-check passed
  • Compose Workflow

    danielvm-git/bigpowers

    Chain multiple bigpowers skills into a custom workflow recipe saved in specs/.

    256 GitHub stars~723 tokensUpdated 16 days ago
    Auto-check passed

Questions about Validate Fix

What does Validate Fix do?

Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Validate Fix is an agent skill from danielvm-git/bigpowers. Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence.

When should I use Validate Fix?

Validate Fix fits situations like: says is this fixed?; before closing an investigation.

How do I install Validate Fix in Claude Code?

Run `npx skills add danielvm-git/bigpowers --skill validate-fix -a claude-code`. Or copy the skill folder (skills/validate-fix in danielvm-git/bigpowers) into .claude/skills/validate-fix in your project. Claude Code loads it when a task matches its description.

How do I install Validate Fix in Codex?

Run `npx skills add danielvm-git/bigpowers --skill validate-fix -a codex`. Or copy the skill folder (skills/validate-fix in danielvm-git/bigpowers) into .agents/skills/validate-fix in your project. Codex loads it when a task matches its description.

Can I use Validate Fix in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill validate-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-fix, .gemini/skills/validate-fix, .github/skills/validate-fix and .opencode/skills/validate-fix in your project.

What does Validate Fix need to run?

Going by SKILL.md and its folder, Validate Fix needs the command-line tools its instructions call (bash).

Does Validate Fix access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Validate Fix safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Validate Fix use?

Validate Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Validate Fix use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Validate Fix?

Skills that share tags, products or a category with Validate Fix: Authoring CI Workflows (PostHog/posthog-foss, 721 stars), React Router Bug Fix Workflow (remix-run/react-router, 57k stars), Adk Setup (google/adk-python, 22k stars) and Runtime Debug (OpenHikmah/openhikmah-web, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Validate Fix?

danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.

Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.