Java changing with tests
v1.0.0Guide Java changes with minimal edits, verify using unit/integration tests as needed, and provide a PR-ready summary including plans, changes, test results,...
⭐ 1· 2.2k·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & 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.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
latestvk97ftrjbyzet2eb16dw9zd4tyx8050hc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.