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

130 Java Testing Strategies

by jabrena in jabrena/plinth

A skill your agent uses when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary…

Apache-2.0Auto-check passedTesting & QA

Install 130 Java Testing Strategies

skills CLI
$ npx skills add jabrena/plinth --skill 130-java-testing-strategies -a claude-code

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

GitHub CLI
$ gh skill install jabrena/plinth 130-java-testing-strategies --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/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/130-java-testing-strategies .claude/skills/130-java-testing-strategies && 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
130-java-testing-strategies
GitHub stars
446
Token cost
~1.3k tokens
SKILL.md length
540 words
Files
4 (incl. references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary…

  • You need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Calls mvn
  • A-TRIP for test quality characteristics

What it does

130 Java Testing Strategies is an agent skill from jabrena/plinth. Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code; Apply A-TRIP testing strategies in Java code; Apply CORRECT boundary condition verification in Java code. Part of Plinth Toolkit

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/130-java-testing-strategies-a-trip.md`, `references/130-java-testing-strategies-correct.md` and `references/130-java-testing-strategies-right-bicep.md`).

It sits in Testing & QA, covering Test strategy and Infrastructure as code. It works with Java and Bicep. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • You need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation
  • A-TRIP for test quality characteristics
  • CORRECT for verifying boundary conditions
  • Requests such as Review Java code for testing strategies

Example prompts

  • “/130-java-testing-strategies”

What it can do on your machine

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

    • mvn

    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

130 Java Testing Strategies loads about 1.3k tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 119 tokens; SKILL.md has 540 words of instructions outside code blocks.

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

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 jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 540 words, ~1,317 tokens.

Download SKILL.mdSave it as .claude/skills/130-java-testing-strategies/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
130-java-testing-strategies
description
Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code; Apply A-TRIP testing strategies in Java code; Apply CORRECT boundary condition verification in Java code. Part of Plinth Toolkit
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

Java testing strategies

Apply proven testing strategies (RIGHT-BICEP, A-TRIP, CORRECT) to design and verify Java unit tests.

What is covered in this Skill?

  • RIGHT-BICEP: Key questions to guide test creation — Right results, Boundary conditions, Inverse relationships, Cross-checks, Error conditions, Performance
  • A-TRIP: Characteristics of good tests — Automatic, Thorough, Repeatable, Independent, Professional
  • CORRECT: Boundary condition verification — Conformance, Ordering, Range, Reference, Existence, Cardinality, Time

Constraints

Before applying any test strategy changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification.

  • MANDATORY: Run ./mvnw compile or mvn compile before applying any change
  • SAFETY: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition
  • VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
  • BEFORE APPLYING: Read only the testing-strategy references selected by the user's concern before changing tests
  • FOCUSED ROUTING: For missing behavior coverage or RIGHT-BICEP requests, read references/130-java-testing-strategies-right-bicep.md by default
  • FOCUSED ROUTING: For flaky, brittle, manual, order-dependent, shared-state, or maintainability requests, read references/130-java-testing-strategies-a-trip.md by default
  • FOCUSED ROUTING: For boundary-condition or CORRECT requests, read references/130-java-testing-strategies-correct.md by default
  • BROAD REVIEW: For broad test-strategy reviews, combine RIGHT-BICEP, A-TRIP, and CORRECT references and categorize findings by technique
  • EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
  • EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
  • EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off

When to use this skill

  • Review Java code for testing strategies
  • Find missing Java test cases or behavior coverage gaps
  • Apply RIGHT-BICEP testing strategies in Java code
  • Review flaky, brittle, order-dependent, or hard-to-maintain Java tests
  • Apply A-TRIP testing strategies in Java code
  • Review Java boundary condition tests
  • Apply CORRECT boundary condition verification in Java code
Show full SKILL.md (217 more words)Show less

Workflow

  1. Compile project before test-strategy changes

Run ./mvnw compile or mvn compile and stop immediately if compilation fails.

  1. Select focused testing-strategy references

Route the request before reading references:

  • Read references/130-java-testing-strategies-right-bicep.md when the request asks what to test, which behavior is missing, whether assertions prove the right result, how to force errors, how to cross-check, or how to add performance guardrails.
  • Read references/130-java-testing-strategies-a-trip.md when the request asks why tests are flaky, brittle, manual, slow to run locally, order-dependent, shared-state dependent, unclear, or hard to maintain.
  • Read references/130-java-testing-strategies-correct.md when the request asks for boundary-condition review, CORRECT analysis, invalid input handling, conformance, ordering, range, external reference, existence, cardinality, or time cases.
  • For broad test-strategy reviews, read all three focused references and organize findings by RIGHT-BICEP, A-TRIP, and CORRECT.

Do not require unrelated references for a narrow request unless the user's concern crosses technique boundaries.

  1. Apply strategy-driven test improvements

Improve or add tests using the selected technique: produce a RIGHT-BICEP gap matrix for missing behavior coverage, an A-TRIP quality finding list for test reliability and maintainability issues, a CORRECT boundary checklist for boundary reviews, or all three sections for broad reviews.

  1. Verify with full build

Run ./mvnw clean verify or mvn clean verify after applying improvements.

Reference

For detailed guidance, examples, and constraints, see:

© jabrena, 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 3 other files (references) in skills/130-java-testing-strategies of jabrena/plinth.

  • SKILL.md
  • references/130-java-testing-strategies-a-trip.md
  • references/130-java-testing-strategies-correct.md
  • references/130-java-testing-strategies-right-bicep.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

130 Java Testing Strategies 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.

130 Java Testing Strategies compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
130 Java Testing Strategies this skilljabrena/plinth446—~1.3kAutomated safety check: PassApache-2.0
Unit Test Boundary Conditionsgiuseppe-trisciuoglio/developer-kit355—~2.3kAutomated safety check: NotesMIT
Java Regression Test GeneratorArabelaTso/Skills-4-SE253—~4kAutomated safety check: PassApache-2.0
Unit Test Parameterizedgiuseppe-trisciuoglio/developer-kit355—~1.6kAutomated safety check: NotesMIT
Writing Testsvert-x3/vertx-redis-client142—~1.6kAutomated safety check: PassApache-2.0
Code Repair Generation ComboArabelaTso/Skills-4-SE253—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Unit Test Boundary Conditions

    giuseppe-trisciuoglio/developer-kit

    Provides edge case, corner case, boundary condition, and limit testing patterns for Java unit tests.

    355 GitHub stars~2.3k tokensUpdated 27 days ago
    Testing & QAAuto-check: notes

  • Java Regression Test Generator

    ArabelaTso/Skills-4-SE

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

    253 GitHub stars~4k tokensUpdated 1 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

  • Writing Tests

    vert-x3/vertx-redis-client

    Testing patterns for Vert.x Redis Client: test frameworks, async testing, test locations, container setup, and how to run tests.

    142 GitHub stars~1.6k tokensUpdated today
    DatabasesAuto-check passed

  • Code Repair Generation Combo

    ArabelaTso/Skills-4-SE

    Automatically repair buggy code and generate comprehensive tests for Python, Java, and C++ programs.

    253 GitHub stars~1.3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Microsoft Skill Creator

    MicrosoftDocs/mcp

    Official

    Create agent skills for Microsoft technologies using official documentation.

    1.9k GitHub starsUsed in 3 repos~2.1k tokens
    Agent WorkflowsAuto-check passed

More from jabrena/plinth

All 124 skills in this repo

  • 703 Technologies Fuzzing Testing

    jabrena/plinth

    A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated today
    Auto-check passed

  • 033 Architecture Diagrams

    jabrena/plinth

    A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    446 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • 112 Java Maven Plugins

    jabrena/plinth

    A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    446 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • 151 Java Performance Jmeter

    jabrena/plinth

    A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    446 GitHub stars~842 tokensUpdated today
    Auto-check passed

  • 161 Java Profiling Detect

    jabrena/plinth

    A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    446 GitHub stars~903 tokensUpdated today
    Auto-check passed

  • 001 Commands Inventory

    jabrena/plinth

    A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    446 GitHub stars~697 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about 130 Java Testing Strategies

What does 130 Java Testing Strategies do?

A skill your agent uses when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary…. 130 Java Testing Strategies is an agent skill from jabrena/plinth. Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions.

When should I use 130 Java Testing Strategies?

130 Java Testing Strategies fits situations like: you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation; A-TRIP for test quality characteristics; CORRECT for verifying boundary conditions; requests such as Review Java code for testing strategies.

How do I install 130 Java Testing Strategies in Claude Code?

Run `npx skills add jabrena/plinth --skill 130-java-testing-strategies -a claude-code`. Or copy the skill folder (skills/130-java-testing-strategies in jabrena/plinth) into .claude/skills/130-java-testing-strategies in your project. Claude Code loads it when a task matches its description.

How do I install 130 Java Testing Strategies in Codex?

Run `npx skills add jabrena/plinth --skill 130-java-testing-strategies -a codex`. Or copy the skill folder (skills/130-java-testing-strategies in jabrena/plinth) into .agents/skills/130-java-testing-strategies in your project. Codex loads it when a task matches its description.

Can I use 130 Java Testing Strategies 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 jabrena/plinth --skill 130-java-testing-strategies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/130-java-testing-strategies, .gemini/skills/130-java-testing-strategies, .github/skills/130-java-testing-strategies and .opencode/skills/130-java-testing-strategies in your project.

What does 130 Java Testing Strategies need to run?

Going by SKILL.md and its folder, 130 Java Testing Strategies needs the command-line tools its instructions call (mvn).

Does 130 Java Testing Strategies 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 130 Java Testing Strategies 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 130 Java Testing Strategies use?

130 Java Testing Strategies is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 130 Java Testing Strategies use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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.6k tokens, read only when the agent opens those files.

What are the alternatives to 130 Java Testing Strategies?

Skills that share tags, products or a category with 130 Java Testing Strategies: Unit Test Boundary Conditions (giuseppe-trisciuoglio/developer-kit, 355 stars), Java Regression Test Generator (ArabelaTso/Skills-4-SE, 253 stars), Unit Test Parameterized (giuseppe-trisciuoglio/developer-kit, 355 stars) and Writing Tests (vert-x3/vertx-redis-client, 142 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 130 Java Testing Strategies?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

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