New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fix

by jvm-skills in jvm-skills/jvm-skills

Fix a bug or missing feature using TDD — write failing test first, then fix, refactor, verify, beautify.

Apache-2.0Auto-check passedTesting & QA

Install Fix

skills CLI
$ npx skills add jvm-skills/jvm-skills --skill fix -a claude-code

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

GitHub CLI
$ gh skill install jvm-skills/jvm-skills 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/jvm-skills/jvm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.junie/skills/fix .claude/skills/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
fix
GitHub stars
139
Token cost
~695 tokens
SKILL.md length
369 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Fix a bug or missing feature using TDD — write failing test first, then fix, refactor, verify, beautify.

  • Works in 8 steps: Understand → Classify — pick test approach → Red — write a failing test → …
  • A bug is discovered
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • A feature doesnt work as expected

What it does

Fix is an agent skill from jvm-skills/jvm-skills. Fix a bug or missing feature using TDD — write failing test first, then fix, refactor, verify, beautify. Use when a bug is discovered or a feature doesn't work as expected.

Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test-driven development and Refactoring. The licence is Apache-2.0.

When your agent uses it

  • A bug is discovered
  • A feature doesnt work as expected

Example prompts

  • “/fix”

Workflow steps

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

  1. Understand
  2. Classify — pick test approach
  3. Red — write a failing test
  4. Green — make the test pass
  5. Refactor
  6. Verify
  7. Beautify (UI fixes only)
  8. Commit

What it can do on your machine

Read from SKILL.md and the folder at commit c6d477f. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Fix loads about 695 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 369 words of instructions outside code blocks.

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

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 jvm-skills/jvm-skills at commit c6d477f, republished under its Apache-2.0 licence (© jvm-skills). 369 words, ~695 tokens.

Download SKILL.mdSave it as .claude/skills/fix/SKILL.md (or your agent's skills folder).
name
fix
description
Fix a bug or missing feature using TDD — write failing test first, then fix, refactor, verify, beautify. Use when a bug is discovered or a feature doesn't work as expected.

Fix with TDD

Fix a bug or missing feature by writing a failing test first, then making it pass.

Process

1. Understand

Describe the bug or missing behavior. Explore the codebase to find the relevant code paths.

  • If UI-related: screenshot the current broken state (if browser automation is available)
  • Find the relevant service, controller, and template/view files
  • Check if there's an existing test class for this area
2. Classify — pick test approach
ScenarioTest approach
Service/repository logic, DB queriesIntegration tests with real DB
File uploads, external storageIntegration tests with mocks/stubs
Browser-visible UI, full user flowsEnd-to-end browser tests
3. Red — write a failing test

⛔ MANDATORY GATE — do NOT write any fix code until this step is complete.

Write a test that reproduces the bug or asserts the missing behavior. Add to an existing test class if one covers this area, otherwise create a new one.

Run /test *FilterPattern and paste the failure output to confirm the test fails for the right reason.

<rules>
- If you cannot write a test, you MUST use AskUserQuestion to explain why and get explicit approval before skipping. Do not rationalize the skip yourself.
- "It's just a template change" is NOT a valid reason to skip — template bugs often have testable service/controller behavior behind them.
- The test name should describe the expected behavior, not the bug (e.g. `Should transition to REVEAL when voting ends` not `Fix end button`)
- If the fix requires a DB migration, do that first: migration → run codegen → then write test
</rules>
Show full SKILL.md (118 more words)Show less
4. Green — make the test pass

Write the minimum code to make the test pass.

  1. Compile the code
  2. Run the test — paste the green output to confirm pass
5. Refactor

Run /simplify to review changed code for reuse, quality, and efficiency. Then clean up anything remaining: remove duplication, extract methods if needed, ensure naming is consistent with surrounding code.

Run the test again — confirm still green after refactoring.

6. Verify
  • UI fixes: /restart-spring-boot → verify the fix (screenshot or browser automation) → compare with the broken state from step 1
  • Backend fixes: test output is sufficient proof
7. Beautify (UI fixes only)

If the fix introduced new UI elements:

design skill → refine → verify the UI

8. Commit

/commit

© jvm-skills, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .junie/skills/fix of jvm-skills/jvm-skills.

Open the folder on GitHubat commit c6d477f

Compare with similar skills

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.

Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix this skilljvm-skills/jvm-skills139—~695Automated safety check: PassApache-2.0
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDD Methodoly Expertthedaviddias/skill-check190—~2.2kAutomated safety check: PassMIT
TDDDanMcInerney/architect-loop626—~730Automated safety check: PassMIT
TDD Workflowaffaan-m/ECC276k1 repos~2.6kAutomated safety check: PassMIT
Test Driven Developmentdzhalaevd/Donatello135—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD Methodoly Expert

    thedaviddias/skill-check

    A skill your agent uses when implementing features or fixing bugs with strict Test-Driven Development (TDD).

    190 GitHub stars~2.2k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • TDD

    DanMcInerney/architect-loop

    Test-driven development for factory builders. An agent skill from DanMcInerney/architect-loop.

    626 GitHub stars~730 tokensUpdated 27 days ago
    Testing & QAAuto-check passed

  • TDD Workflow

    affaan-m/ECC

    Yeni özellikler yazarken, hata düzeltirken veya kod refactor ederken bu skill'i kullanın.

    276k GitHub starsUsed in 1 repo~2.6k tokens
    Testing & QAAuto-check passed

  • Test Driven Development

    dzhalaevd/Donatello

    Use as a workflow overlay when implementing any feature, bugfix, refactor, or behavior change before writing production code

    135 GitHub stars~1.1k tokensUpdated 7 days ago
    Testing & QAAuto-check passed

  • TDD

    nodetool-ai/nodetool

    Develop a behavior test-first through red, green, and refactoring.

    560 GitHub stars~906 tokensUpdated today
    Testing & QAAuto-check passed

More from jvm-skills/jvm-skills

All 16 skills in this repo

  • Mutation Testing

    jvm-skills/jvm-skills

    Bootstrap pitest via the info.solidsoft.pitest Gradle plugin with Kotlin-sane defaults, run mutation tests scoped to changed classes, interpret surviving mutants from mutations.xml, triage…

    139 GitHub stars~6.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Ralph Coverage

    jvm-skills/jvm-skills

    Run Ralph in coverage mode — iteratively write tests for untested classes until coverage targets are met.

    139 GitHub stars~683 tokensUpdated 1 mo ago
    Auto-check passed

  • Skill Scout

    jvm-skills/jvm-skills

    Run the skill-scout loop — scan the next batch of unscanned JVM-conference rosters for speaker-created AI skills and apply results to the CSV store via the overnight Workflow.

    139 GitHub stars~727 tokensUpdated 1 mo ago
    Auto-check passed

  • Spec

    jvm-skills/jvm-skills

    Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed.

    139 GitHub stars~832 tokensUpdated 1 mo ago
    Auto-check passed

  • UI Review

    jvm-skills/jvm-skills

    Verify UI/UX by running Playwright tests and reviewing screenshots.

    139 GitHub stars~545 tokensUpdated 1 mo ago
    Auto-check passed

  • Kotest

    jvm-skills/jvm-skills

    Write a new Kotlin test, or modernize an existing one, using Kotest matchers and idiomatic Kotlin test style — backticked names, apply/assertSoftly blocks, and existing object mothers and helpers.

    139 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Fix

What does Fix do?

Fix a bug or missing feature using TDD — write failing test first, then fix, refactor, verify, beautify. Fix is an agent skill from jvm-skills/jvm-skills. Fix a bug or missing feature using TDD — write failing test first, then fix, refactor, verify, beautify.

When should I use Fix?

Fix fits situations like: A bug is discovered; A feature doesnt work as expected.

How do I install Fix in Claude Code?

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

How do I install Fix in Codex?

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

Can I use 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 jvm-skills/jvm-skills --skill 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/fix, .gemini/skills/fix, .github/skills/fix and .opencode/skills/fix in your project.

What does Fix need to run?

SKILL.md names no scripts, command-line tools or credentials: Fix is instructions for the agent only.

Does 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 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 Fix use?

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

How many tokens does Fix use?

About 695 tokens (SKILL.md is roughly 2.8k 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 Fix?

Skills that share tags, products or a category with Fix: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD Methodoly Expert (thedaviddias/skill-check, 190 stars), TDD (DanMcInerney/architect-loop, 626 stars) and TDD Workflow (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix?

jvm-skills (a GitHub organization) maintains it in jvm-skills/jvm-skills, which has 139 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on August 31, 2026.

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