Best for
- Review Java code for testing strategies
- Find missing Java test cases or behavior coverage gaps
- Apply RIGHT-BICEP testing strategies in Java code
Source profileQuality 89/100
jabrena/plinth/skills/130-java-testing-strategies/SKILL.md
130-java-testing-strategies
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
- Source repository stars
- 423
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-02
- Source checked
- 2026-08-04
Decision brief
What it does—and where it fits
Apply proven testing strategies (RIGHT-BICEP, A-TRIP, CORRECT) to design and verify Java unit tests.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/jabrena/plinth --skill "skills/130-java-testing-strategies"Safe inspection promptEditorial
Inspect the Agent Skill "130-java-testing-strategies" from https://github.com/jabrena/plinth/blob/fdaf68ccf0ffc4fb6147dc4ab805c34841ffaf33/skills/130-java-testing-strategies/SKILL.md at commit fdaf68ccf0ffc4fb6147dc4ab805c34841ffaf33. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Workflow
1. Compile project before test-strategy changes
Compile project before test-strategy changesSelect focused testing-strategy referencesRead 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… - 02
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 changeSAFETY: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking conditionVERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements - 03
When to use this skill
Review Java code for testing strategies
Review Java code for testing strategiesFind missing Java test cases or behavior coverage gapsApply RIGHT-BICEP testing strategies in Java code
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 89/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 423 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- jabrena/plinth
- Skill path
- skills/130-java-testing-strategies/SKILL.md
- Commit
- fdaf68ccf0ffc4fb6147dc4ab805c34841ffaf33
- License
- Apache-2.0
- Collected
- 2026-08-04
- Default branch
- main
View the original SKILL.md
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 compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter 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.mdby default - FOCUSED ROUTING: For flaky, brittle, manual, order-dependent, shared-state, or maintainability requests, read
references/130-java-testing-strategies-a-trip.mdby default - FOCUSED ROUTING: For boundary-condition or CORRECT requests, read
references/130-java-testing-strategies-correct.mdby 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
Workflow
- Compile project before test-strategy changes
Run ./mvnw compile or mvn compile and stop immediately if compilation fails.
- Select focused testing-strategy references
Route the request before reading references:
- Read
references/130-java-testing-strategies-right-bicep.mdwhen 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.mdwhen 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.mdwhen 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.
- 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.
- Verify with full build
Run ./mvnw clean verify or mvn clean verify after applying improvements.
Reference
For detailed guidance, examples, and constraints, see:
Alternatives
Compare before choosing
Computed 10023,781
alirezarezvani/claude-skills
app-store-optimization
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
Computed 1004,922
dotnet/skills
migrate-vstest-to-mtp
Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing
Computed 984,922
dotnet/skills
maui-dependency-injection
Guidance for configuring dependency injection in .NET MAUI apps — service registration in MauiProgram.cs, lifetime selection (Singleton / Transient / Scoped), constructor injection, Shell navigation auto-resolution, platform-specific registrations, and testability patterns. USE FOR: "dependency injection", "DI setup", "AddSingleton", "AddTransient", "AddScoped", "service registration", "constructor injection", "IServiceProvider", "MauiProgram DI", "register services", "BindingContext injection".
Computed 983,251
davepoon/buildwithclaude
circleci-automation
Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.