← Back to Skills Marketplace
Java changing with tests
by
tanerilyazov
· GitHub ↗
· v1.0.0
2229
Downloads
1
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install java-change-with-tests
Description
Guide Java changes with minimal edits, verify using unit/integration tests as needed, and provide a PR-ready summary including plans, changes, test results,...
README (SKILL.md)
java-change-with-tests
When to use
- Any Java change that must be merged safely (feature/refactor/bugfix).
Inputs to request (if missing)
- Acceptance criteria (1-3 bullets).
- Module name (if multi-module repo).
- Build tool and test conventions.
- Whether integration tests are required for the change.
Steps
- Repo map (brief): identify the module, entrypoint, and test location.
- Plan: smallest diff that meets acceptance criteria.
- Implement: minimal edits.
- Tests:
- prefer fast unit tests first
- add integration tests only when required to validate behavior
- Verify:
- run targeted tests
- run
mvn -q test(or module-scoped equivalent)
- Output PR-ready summary with evidence.
Verification commands (project-specific)
- Use the repo's build tool and record the exact commands and results.
- Prefer targeted unit tests before full test suites.
Output contract
- Plan (3-6 steps)
- Files changed + intent
- Commands run + results
- Risks + follow-ups
Usage Guidance
This is an instruction-only workflow for making Java changes and running tests — it's internally consistent and low risk. Before installing or using it, confirm the agent has: (1) explicit access to the repository you want it to edit, (2) the appropriate build tool (e.g., Maven) is available on the environment where the agent runs, and (3) any git/CI credentials remain under your control (the skill does not request them but the agent will need them to push or open PRs). Also consider restricting the agent's ability to push commits or open PRs automatically (require manual approval) if you don't want autonomous writes to your repo. If you want the skill to be more robust, ask the developer to (a) add a short description to the metadata, and (b) document required binaries (mvn/gradle) and expected repository access/permissions.
Capability Analysis
Type: OpenClaw Skill
Name: java-change-with-tests
Version: 1.0.0
The skill bundle is benign. The `SKILL.md` and `README.md` files describe a standard workflow for making Java code changes, including planning, implementation, testing, and verification using common build tools like Maven. All instructions for the AI agent, such as mapping the repository and running `mvn` commands, are directly aligned with the stated purpose and do not exhibit any signs of data exfiltration, malicious execution, persistence, or prompt injection with harmful intent.
Capability Assessment
Purpose & Capability
The skill's name and SKILL.md describe a minimal-diff + tests workflow for Java projects, which aligns with the steps it instructs (identify module, implement, run tests, produce PR-ready output). Minor incoherence: the skill doesn't include a description in the metadata and the manifest declares no required binaries, yet the instructions assume use of a build tool (maven/`mvn`) — the skill should declare that the build tool must exist or prompt for it.
Instruction Scope
Instructions stay within the stated purpose: mapping repo, creating a minimal plan, implementing code, running targeted unit/integration tests, and reporting commands/results. The steps reference running project build/test commands and producing a PR summary; they do not instruct reading unrelated system files or exfiltrating data.
Install Mechanism
No install spec and no code files (instruction-only). This is low-risk: nothing is downloaded or written by an installer. The skill relies on the environment having the project's build tools available.
Credentials
The skill declares no required environment variables or credentials and its requested operations (editing repo files and running tests) do not require additional secrets. Note: to operate the agent will need access to the repository files and any developer credentials (git push/CI) are external to the skill and are not requested — which is appropriate.
Persistence & Privilege
always is false and there is no install that modifies agent configuration. The skill does not request persistent presence or system-wide changes.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install java-change-with-tests - After installation, invoke the skill by name or use
/java-change-with-tests - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of db-backfill-safe skill.
- Provides a step-by-step guide for making safe Java code changes with test coverage.
- Lists required inputs such as acceptance criteria, module name, and test conventions.
- Outlines the process: repo mapping, planning, minimal implementation, targeted testing, verification, and outputting a summary.
- Specifies verification and output standards for pull request readiness.
Metadata
Frequently Asked Questions
What is Java changing with tests?
Guide Java changes with minimal edits, verify using unit/integration tests as needed, and provide a PR-ready summary including plans, changes, test results,... It is an AI Agent Skill for Claude Code / OpenClaw, with 2229 downloads so far.
How do I install Java changing with tests?
Run "/install java-change-with-tests" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Java changing with tests free?
Yes, Java changing with tests is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Java changing with tests support?
Java changing with tests is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Java changing with tests?
It is built and maintained by tanerilyazov (@tanerilyazov); the current version is v1.0.0.
More Skills