agentsclimarketplace
Sign in

Test and fix

Skill yu-iskw/coding-agent-fabric/.claude/skills/test-and-fix

Run unit tests and automatically fix code failures, regression bugs, or test mismatches. Use when tests are failing, after implementing new features, or to repair "broken" tests.From its SKILL.md

Install
npx -y skills add yu-iskw/coding-agent-fabric --skill test-and-fix

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 442 tokens by cl100k_base, as published. Nobody here has run it

Test and Fix Loop

Purpose

An autonomous loop for the agent to identify, analyze, and fix failing unit tests using Vitest.

Loop Logic

  1. Identify: Run pnpm test to identify failing tests.
  2. Analyze: Examine the test output to determine:
  3. Fix: Apply the minimum necessary change to either the source code (if it's a bug) or the test code (if the test is outdated).
  4. Verify: Re-run pnpm test.
    • If passed: Move to the next failing test or finish if all are resolved.
    • If failed: Analyze the new failure (or the same one if the fix was insufficient) and repeat the loop.

Termination Criteria

  • All tests pass (as reported by pnpm test).
  • Reached max iteration limit (default: 5).
  • The error persists after multiple distinct fix attempts, indicating a need for human intervention or a broader architectural change.

Examples

Scenario: Fixing a logic error

  1. pnpm test fails in packages/common/src/math.test.ts because add(2, 2) returned 5.
  2. Agent analyzes packages/common/src/math.ts and finds a typo a + b + 1.
  3. Agent fixes the typo to a + b.
  4. pnpm test passes.

Scenario: Updating a test after a deliberate change

  1. pnpm test fails because a UI component's text changed from "Submit" to "Confirm".
  2. Agent confirms the change was intentional.
  3. pnpm test passes.

Resources

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most test skills give in 442 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

  • Close the browser when donein 55 of 964, across 12 files
  • Wait for network idle statein 51 of 964, across 6 files
  • Launch Chromium in headless modein 49 of 964, across 6 files
  • Use descriptive selectors for elementsin 49 of 964, across 6 files
  • Run provided scripts with help flag firstin 49 of 964, across 6 files
  • Add appropriate explicit waitsin 48 of 964, across 5 files
  • Use bundled scripts as black boxesin 46 of 964, across 3 files
  • Do not read script source codein 46 of 964, across 3 files
  • Use sync playwright for scriptsin 46 of 964, across 3 files
  • Inspect dom before executing actionsin 46 of 964, across 3 files
  • Run the full test suitein 37 of 964
  • Write the failing test firstin 29 of 964, across 23 files

Said here and by no other author read

  • examine the test output for expected and actual values
  • apply the minimum necessary change to fix the failure
  • stop after reaching the maximum iteration limit
  • stop if the error persists after multiple distinct attempts

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,790. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.