Agent skill

Java Regression Test Generator

by ArabelaTso in ArabelaTso/Skills-4-SE

Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions.

Apache-2.0Auto-check passedTesting & QA

Install Java Regression Test Generator

skills CLI
$ npx skills add ArabelaTso/Skills-4-SE --skill java-regression-test-generator -a claude-code

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

GitHub CLI
$ gh skill install ArabelaTso/Skills-4-SE java-regression-test-generator --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/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/java-regression-test-generator .claude/skills/java-regression-test-generator && 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
java-regression-test-generator
GitHub stars
253
Token cost
~4k tokens
SKILL.md length
732 words
Files
3 (incl. references)
Skills in repo
151
Repo updated
First seen
Licence
Apache-2.0

At a glance

Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions.

  • Works in 5 steps: Analyze Code Changes → Classify Change Types → Determine Test Strategy → …
  • Generate tests after refactoring
  • SKILL.md covers Overview, How to Use, Test Generation Workflow and Example: Parameter Added, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Java Regression Test Generator is an agent skill from ArabelaTso/Skills-4-SE. Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions. Use when users need to: (1) Generate tests after refactoring or code changes, (2) Ensure previously tested behavior still works in new versions, (3) Cover modified or newly added code paths, (4) Migrate existing tests to work with updated APIs or signatures, (5) Maintain test coverage during code evolution. Supports JUnit and TestNG frameworks with unit tests, parameterized tests, and exception…

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/change_patterns.md` and `references/test_patterns.md`).

It sits in Testing & QA, covering Unit testing, Test generation and Test strategy. It works with Java and JUnit. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.

When your agent uses it

  • Generate tests after refactoring
  • Ensure previously tested behavior still works in new versions
  • Newly added code paths
  • Migrate existing tests to work with updated APIs

Example prompts

  • “/java-regression-test-generator”

Workflow steps

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

  1. Analyze Code Changes
  2. Classify Change Types
  3. Determine Test Strategy
  4. Generate Regression Tests
  5. Handle Invalid Tests

What it can do on your machine

Read from SKILL.md and the folder at commit 4f38503. 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 (its code samples are java).

    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

Java Regression Test Generator loads about 4k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 140 tokens; SKILL.md has 732 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~140
When it runs · the whole SKILL.md, loaded when a task matches
~4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~10k

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 ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 732 words, ~4,003 tokens.

Download SKILL.mdSave it as .claude/skills/java-regression-test-generator/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
java-regression-test-generator
description
Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions. Use when users need to: (1) Generate tests after refactoring or code changes, (2) Ensure previously tested behavior still works in new versions, (3) Cover modified or newly added code paths, (4) Migrate existing tests to work with updated APIs or signatures, (5) Maintain test coverage during code evolution. Supports JUnit and TestNG frameworks with unit tests, parameterized tests, and exception testing patterns.

Java Regression Test Generator

Automatically generate regression tests for Java code based on version changes.

Overview

This skill analyzes changes between old and new versions of Java code and generates regression tests that ensure previously tested behavior still works while covering new or modified functionality. It preserves correctness guarantees from existing tests and suggests updates when old tests become invalid.

How to Use

Provide:

  1. Old version: The previous version of Java code
  2. New version: The updated version of Java code
  3. Existing tests: Test classes or methods for the old version
  4. Framework (optional): JUnit 5 (default) or TestNG

The skill will:

  • Analyze changes between versions
  • Identify modified, added, or removed functionality
  • Generate regression tests for the new code
  • Suggest updates for invalid existing tests
  • Produce executable test code ready for integration

Test Generation Workflow

Step 1: Analyze Code Changes

Compare old and new versions to identify changes:

Method-level changes:

  • Signature changes (parameters, return type)
  • Logic modifications (algorithm, error handling)
  • New methods added
  • Methods removed

Class-level changes:

  • Field additions or removals
  • Constructor changes
  • Inheritance modifications
  • Access modifier changes

Dependency changes:

  • New dependencies injected
  • Dependency injection patterns added
  • External API changes
Step 2: Classify Change Types

Categorize each change to determine test generation strategy:

Type 1: Signature Changes

  • Parameter added/removed/reordered
  • Return type changed
  • Exception declarations modified

Type 2: Behavioral Changes

  • Algorithm optimized (same behavior)
  • Error handling added
  • Validation logic added

Type 3: Structural Changes

  • New methods/classes added
  • Methods/classes removed
  • Refactoring (extract method, rename)

Type 4: Dependency Changes

  • Constructor injection added
  • Dependencies replaced
  • Mock requirements changed
Step 3: Determine Test Strategy

For each change type, decide on test generation approach:

Change TypeStrategy
Parameter addedMigrate existing tests + generate new parameter tests
Return type changedUpdate assertions + add new type-specific tests
New methodGenerate full test coverage (normal, edge, error cases)
Logic optimizedPreserve existing tests + add performance/edge tests
Error handling addedPreserve existing tests + add exception tests
Method removedMark tests as obsolete, suggest removal
Dependency injectionUpdate test setup with mocks

See change_patterns.md for detailed strategies.

Step 4: Generate Regression Tests

Create test code following these principles:

Preserve existing behavior:

  • Keep all tests that verify unchanged functionality
  • Migrate tests when signatures change but behavior is preserved
  • Maintain test names and structure when possible

Cover new functionality:

  • Generate tests for new methods
  • Add tests for new parameters or return types
  • Test new error conditions

Ensure quality:

  • Use appropriate assertions
  • Include setup/teardown code
  • Add mocks for dependencies
  • Follow framework conventions (JUnit 5 or TestNG)
Step 5: Handle Invalid Tests

When existing tests become invalid, suggest updates:

Scenario 1: Signature changed

java
// Old test (invalid)
@Test
public void testCalculateDiscount() {
    assertEquals(10, calculator.calculateDiscount(100));
}

// Suggested update
@Test
public void testCalculateDiscount_WithDefaultPercent() {
    // Updated to use new signature with default value
    assertEquals(10, calculator.calculateDiscount(100, 10));
}

Scenario 2: Return type changed

java
// Old test (invalid)
@Test
public void testGetUser() {
    User user = service.getUser("123");
    assertEquals("John", user.getName());
}

// Suggested update
@Test
public void testGetUser() {
    Optional<User> userOpt = service.getUser("123");
    assertTrue(userOpt.isPresent());
    assertEquals("John", userOpt.get().getName());
}

Scenario 3: Method removed

java
// Old test (obsolete)
// @Test
// public void testDeprecatedMethod() {
//     service.deprecatedMethod();
// }
// OBSOLETE: deprecatedMethod() removed in new version
// Consider: Check if functionality moved to another method
Show full SKILL.md (293 more words)Show less

Example: Parameter Added

Old Code:

java
public class DiscountCalculator {
    public int calculateDiscount(int price) {
        return price * 10 / 100;  // Fixed 10% discount
    }
}

New Code:

java
public class DiscountCalculator {
    public int calculateDiscount(int price, int discountPercent) {
        return price * discountPercent / 100;  // Configurable discount
    }
}

Existing Test:

java
@Test
public void testCalculateDiscount() {
    DiscountCalculator calc = new DiscountCalculator();
    assertEquals(10, calc.calculateDiscount(100));
}

@Test
public void testCalculateDiscount_LargeAmount() {
    DiscountCalculator calc = new DiscountCalculator();
    assertEquals(100, calc.calculateDiscount(1000));
}

Generated Regression Tests:

java
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;

public class DiscountCalculatorTest {
    private DiscountCalculator calculator = new DiscountCalculator();

    // Migrated tests - preserve original behavior with default 10%
    @Test
    public void testCalculateDiscount_WithDefaultPercent() {
        // Migrated from testCalculateDiscount
        // Uses 10% to match old behavior
        assertEquals(10, calculator.calculateDiscount(100, 10));
    }

    @Test
    public void testCalculateDiscount_LargeAmount_WithDefaultPercent() {
        // Migrated from testCalculateDiscount_LargeAmount
        assertEquals(100, calculator.calculateDiscount(1000, 10));
    }

    // New tests for added parameter
    @Test
    public void testCalculateDiscount_WithCustomPercent() {
        assertEquals(25, calculator.calculateDiscount(100, 25));
        assertEquals(50, calculator.calculateDiscount(200, 25));
    }

    @Test
    public void testCalculateDiscount_WithZeroPercent() {
        assertEquals(0, calculator.calculateDiscount(100, 0));
    }

    @Test
    public void testCalculateDiscount_WithHundredPercent() {
        assertEquals(100, calculator.calculateDiscount(100, 100));
    }

    @Test
    public void testCalculateDiscount_WithNegativePercent() {
        // Edge case: negative discount
        assertEquals(-10, calculator.calculateDiscount(100, -10));
    }
}

Analysis:

  • Change type: Parameter added (discountPercent)
  • Strategy: Migrate existing tests + generate new parameter tests
  • Preserved: Original test logic with default 10% discount
  • Added: Tests for various discount percentages (0%, 25%, 100%, negative)

Example: New Method Added

Old Code:

java
public class UserService {
    private UserRepository repository;

    public UserService(UserRepository repository) {
        this.repository = repository;
    }

    public User getUser(String id) {
        return repository.findById(id);
    }
}

New Code:

java
public class UserService {
    private UserRepository repository;

    public UserService(UserRepository repository) {
        this.repository = repository;
    }

    public User getUser(String id) {
        return repository.findById(id);
    }

    // New method added
    public List<User> getUsersByRole(String role) {
        return repository.findAll().stream()
            .filter(u -> u.getRole().equals(role))
            .collect(Collectors.toList());
    }
}

Existing Tests:

java
@Test
public void testGetUser() {
    UserRepository mockRepo = mock(UserRepository.class);
    when(mockRepo.findById("123")).thenReturn(new User("123", "John", "admin"));

    UserService service = new UserService(mockRepo);
    User user = service.getUser("123");

    assertEquals("John", user.getName());
}

Generated Regression Tests:

java
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.BeforeEach;
import static org.junit.jupiter.api.Assertions.*;
import static org.mockito.Mockito.*;

public class UserServiceTest {
    private UserRepository mockRepository;
    private UserService service;

    @BeforeEach
    public void setup() {
        mockRepository = mock(UserRepository.class);
        service = new UserService(mockRepository);
    }

    // Existing test preserved
    @Test
    public void testGetUser() {
        when(mockRepository.findById("123"))
            .thenReturn(new User("123", "John", "admin"));

        User user = service.getUser("123");

        assertEquals("John", user.getName());
        verify(mockRepository).findById("123");
    }

    // New tests for getUsersByRole method
    @Test
    public void testGetUsersByRole_WithMatchingUsers() {
        List<User> allUsers = Arrays.asList(
            new User("1", "John", "admin"),
            new User("2", "Jane", "user"),
            new User("3", "Bob", "admin")
        );
        when(mockRepository.findAll()).thenReturn(allUsers);

        List<User> admins = service.getUsersByRole("admin");

        assertEquals(2, admins.size());
        assertTrue(admins.stream().allMatch(u -> u.getRole().equals("admin")));
        verify(mockRepository).findAll();
    }

    @Test
    public void testGetUsersByRole_NoMatches() {
        List<User> allUsers = Arrays.asList(
            new User("1", "John", "user"),
            new User("2", "Jane", "user")
        );
        when(mockRepository.findAll()).thenReturn(allUsers);

        List<User> admins = service.getUsersByRole("admin");

        assertTrue(admins.isEmpty());
    }

    @Test
    public void testGetUsersByRole_EmptyRepository() {
        when(mockRepository.findAll()).thenReturn(Collections.emptyList());

        List<User> users = service.getUsersByRole("admin");

        assertTrue(users.isEmpty());
    }

    @Test
    public void testGetUsersByRole_NullRole() {
        List<User> allUsers = Arrays.asList(
            new User("1", "John", "admin")
        );
        when(mockRepository.findAll()).thenReturn(allUsers);

        assertThrows(NullPointerException.class, () -> {
            service.getUsersByRole(null);
        });
    }
}

Analysis:

  • Change type: New method added (getUsersByRole)
  • Strategy: Preserve existing tests + generate full coverage for new method
  • Preserved: testGetUser remains unchanged
  • Added: 4 tests covering normal case, no matches, empty repository, null input

Example: Return Type Changed

Old Code:

java
public class UserService {
    public User getUserById(String id) {
        return database.findUser(id);  // Returns null if not found
    }
}

New Code:

java
public class UserService {
    public Optional<User> getUserById(String id) {
        return Optional.ofNullable(database.findUser(id));
    }
}

Existing Tests:

java
@Test
public void testGetUserById_ExistingUser() {
    User user = service.getUserById("123");
    assertNotNull(user);
    assertEquals("John", user.getName());
}

@Test
public void testGetUserById_NonExistentUser() {
    User user = service.getUserById("999");
    assertNull(user);
}

Generated Regression Tests:

java
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;
import java.util.Optional;

public class UserServiceTest {
    private UserService service = new UserService();

    // Updated tests for Optional return type
    @Test
    public void testGetUserById_ExistingUser() {
        // Migrated: Updated to handle Optional
        Optional<User> userOpt = service.getUserById("123");

        assertTrue(userOpt.isPresent(), "User should be present");
        assertEquals("John", userOpt.get().getName());
    }

    @Test
    public void testGetUserById_NonExistentUser() {
        // Migrated: Updated to check for empty Optional
        Optional<User> userOpt = service.getUserById("999");

        assertFalse(userOpt.isPresent(), "User should not be present");
    }

    // New tests for Optional-specific behavior
    @Test
    public void testGetUserById_OptionalChaining() {
        Optional<User> userOpt = service.getUserById("123");

        String name = userOpt
            .map(User::getName)
            .orElse("Unknown");

        assertEquals("John", name);
    }

    @Test
    public void testGetUserById_OrElseThrow() {
        Optional<User> userOpt = service.getUserById("999");

        assertThrows(NoSuchElementException.class, () -> {
            userOpt.orElseThrow();
        });
    }
}

Analysis:

  • Change type: Return type changed (User → Optional<User>)
  • Strategy: Update existing tests + add Optional-specific tests
  • Updated: Both existing tests adapted to handle Optional
  • Added: Tests for Optional chaining and orElseThrow behavior

Output Format

Generated tests follow this structure:

java
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.AfterEach;
import static org.junit.jupiter.api.Assertions.*;
import static org.mockito.Mockito.*;

/**
 * Regression tests for [ClassName]
 * Generated from version comparison
 */
public class [ClassName]Test {
    // Test fixtures
    private [ClassName] instance;
    private [Dependency] mockDependency;

    @BeforeEach
    public void setup() {
        // Initialize test fixtures
        mockDependency = mock([Dependency].class);
        instance = new [ClassName](mockDependency);
    }

    @AfterEach
    public void teardown() {
        // Cleanup if needed
    }

    // Preserved tests (migrated if needed)
    @Test
    public void test[MethodName]_[Scenario]() {
        // Arrange
        // Act
        // Assert
    }

    // New tests for added/modified functionality
    @Test
    public void test[NewMethod]_[Scenario]() {
        // Arrange
        // Act
        // Assert
    }
}

References

Detailed patterns and examples:

  • change_patterns.md: Comprehensive catalog of code change types and corresponding test generation strategies
  • test_patterns.md: JUnit and TestNG patterns for unit tests, mocking, parameterized tests, and exception testing

Load these references when:

  • Need detailed examples for specific change types
  • Want to see complete test patterns for JUnit/TestNG
  • Working with complex scenarios (inheritance changes, dependency injection)

Tips

  1. Analyze changes carefully: Understand what changed and why before generating tests
  2. Preserve test intent: Keep the purpose of existing tests even when updating syntax
  3. Cover edge cases: Generate tests for boundary conditions and error scenarios
  4. Use appropriate mocks: Mock external dependencies to isolate unit behavior
  5. Follow naming conventions: Use descriptive test names that explain what is being tested
  6. Maintain readability: Generate clean, well-structured test code
  7. Verify compilation: Ensure generated tests compile with the new code
  8. Check for redundancy: Avoid generating tests that duplicate existing coverage

© ArabelaTso, 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

SKILL.md and 2 other files (references) in skills/java-regression-test-generator of ArabelaTso/Skills-4-SE.

  • SKILL.md
  • references/change_patterns.md
  • references/test_patterns.md

Open the folder on GitHubat commit 4f38503

Compare with similar skills

Java Regression Test Generator 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.

Java Regression Test Generator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Java Regression Test Generator this skillArabelaTso/Skills-4-SE253—~4kAutomated safety check: PassApache-2.0
TDD GuideLeoYeAI/openclaw-master-skills2.2k—~1.4kAutomated safety check: PassMIT
Unit Test Parameterizedgiuseppe-trisciuoglio/developer-kit355—~1.6kAutomated safety check: NotesMIT
Senior QAalirezarezvani/claude-skills28k1 repos~2.1kAutomated safety check: PassMIT
TDD Guidealirezarezvani/claude-skills28k—~3.4kAutomated safety check: PassMIT
Test Qualitydecebals/claude-code-java750—~3.8kAutomated safety check: PassMIT

Similar skills

  • TDD Guide

    LeoYeAI/openclaw-master-skills

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…

    2.2k GitHub stars~1.4k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Unit Test Parameterized

    giuseppe-trisciuoglio/developer-kit

    Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource.

    355 GitHub stars~1.6k tokensUpdated 27 days ago
    Testing & QAAuto-check: notes
  • Senior QA

    alirezarezvani/claude-skills

    Generates unit tests, integration tests, and E2E tests for React/Next.js applications.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check passed
  • TDD Guide

    alirezarezvani/claude-skills

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…

    28k GitHub stars~3.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Test Quality

    decebals/claude-code-java

    Write high-quality JUnit 5 tests with AssertJ assertions. An agent skill from decebals/claude-code-java.

    750 GitHub stars~3.8k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Memstack Development Test Writer

    cwinvestments/memstack

    A skill your agent uses when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with…

    423 GitHub stars~3.7k tokensUpdated 11 days ago
    Testing & QAAuto-check passed

More from ArabelaTso/Skills-4-SE

All 151 skills in this repo
  • Framework Migration Assistant

    ArabelaTso/Skills-4-SE

    Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).

    253 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Metamorphic Test Generator

    ArabelaTso/Skills-4-SE

    Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.

    253 GitHub stars~798 tokensUpdated 1 mo ago
    Auto-check passed
  • Reproduction Trace Instrumenter

    ArabelaTso/Skills-4-SE

    Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.

    253 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Spring Mvc To Boot Migrator

    ArabelaTso/Skills-4-SE

    Automatically migrate Spring MVC applications to Spring Boot.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • State Snapshot Instrumenter

    ArabelaTso/Skills-4-SE

    Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Java Regression Test Generator

What does Java Regression Test Generator do?

Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions. Java Regression Test Generator is an agent skill from ArabelaTso/Skills-4-SE. Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions.

When should I use Java Regression Test Generator?

Java Regression Test Generator fits situations like: generate tests after refactoring; ensure previously tested behavior still works in new versions; newly added code paths; migrate existing tests to work with updated APIs.

How do I install Java Regression Test Generator in Claude Code?

Run `npx skills add ArabelaTso/Skills-4-SE --skill java-regression-test-generator -a claude-code`. Or copy the skill folder (skills/java-regression-test-generator in ArabelaTso/Skills-4-SE) into .claude/skills/java-regression-test-generator in your project. Claude Code loads it when a task matches its description.

How do I install Java Regression Test Generator in Codex?

Run `npx skills add ArabelaTso/Skills-4-SE --skill java-regression-test-generator -a codex`. Or copy the skill folder (skills/java-regression-test-generator in ArabelaTso/Skills-4-SE) into .agents/skills/java-regression-test-generator in your project. Codex loads it when a task matches its description.

Can I use Java Regression Test Generator 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 ArabelaTso/Skills-4-SE --skill java-regression-test-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/java-regression-test-generator, .gemini/skills/java-regression-test-generator, .github/skills/java-regression-test-generator and .opencode/skills/java-regression-test-generator in your project.

What does Java Regression Test Generator need to run?

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

Does Java Regression Test Generator 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 Java Regression Test Generator 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 Java Regression Test Generator use?

Java Regression Test Generator 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 Java Regression Test Generator use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.3k tokens, read only when the agent opens those files.

What are the alternatives to Java Regression Test Generator?

Skills that share tags, products or a category with Java Regression Test Generator: TDD Guide (LeoYeAI/openclaw-master-skills, 2.2k stars), Unit Test Parameterized (giuseppe-trisciuoglio/developer-kit, 355 stars), Senior QA (alirezarezvani/claude-skills, 28k stars) and TDD Guide (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Java Regression Test Generator?

ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 151 skills in this directory. The repository was last updated on August 21, 2026.

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