ralph-coverage

Automate iterative test writing for untested JVM classes.

135|25|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jvm-skills/jvm-skills --skill ralph-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-coverage
Source: https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ralph-coverage
Command: npx skills add https://github.com/jvm-skills/jvm-skills --skill ralph-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates targeted test-coverage improvements by iteratively writing tests for untested classes.

Core Features & Use Cases

  • Iterative testing workflow: automatically selects the highest-priority untested class and writes tests.
  • Progress tracking: reads and updates progress.txt and PRD.md guidance.
  • One-class-per-iteration discipline: ensures focused changes and clean commits.
  • Headless loop options: afk-ralph.sh for long runs or ralph-once.sh for single iteration.

Quick Start

Run a single coverage iteration using the ralph-once.sh script to start automatically generating tests for the highest-priority untested class.

Frequently Asked Questions about ralph-coverage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate test coverage improvements for untested JVM classes?

Automate test coverage improvements by running a script that iteratively selects the highest-priority untested JVM class, writes tests, runs them, commits changes, and updates a progress log.

What is the one-class-per-iteration approach for writing unit tests?

The one-class-per-iteration approach ensures focused test development by automatically writing tests for a single untested class, running them, and committing the changes before moving to the next class.

How do I track test coverage progress across multiple iterations?

Track test coverage progress by maintaining a progress.txt file that the automation script reads and updates after each iteration, alongside coverage goals defined in PRD.md.

Can I run automated test generation continuously in a headless CI workflow?

Yes, you can run automated test generation continuously in a headless CI workflow using a dedicated script for long runs, or execute a single iteration script for one-off coverage improvements.

Do I need to define coverage goals before automating unit test generation?

Yes, you need to define coverage goals in a PRD.md file before starting the automated unit test generation workflow so the script can coordinate its iterations with your project requirements.

What's the best way to write unit tests for untested classes in a JVM project?

The best way to write unit tests for untested JVM classes is to use an iterative automation script that enforces one-class-per-iteration discipline, ensuring focused changes and clean git commits.