Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentscope-ai/verify-changes
Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.
Passed 10 of 16 test cases with the skill, and 10 of 16 without it.
and 2 more in the full report
4 fixed11 passed either way4 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I modified `app/models/user.py` and `tests/test_user.py`. The team usually runs tests on the entire repo. Which command should we run to check just these files cleanly without terminal colors?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies verification commands targeting app/models/user.py plus tests/test_user.py specifically. | Missed | Passed |
| Suppresses terminal color output using NO_COLOR=1. | Missed | Passed |
The instructions your model reads when the skill loads.
Editing a file is only half a step. Always close the loop by verifying before you mark work done or open a PR. This is the manual equivalent of an IDE/LSP diagnostics loop.
package.json scripts (build, lint, typecheck), tsconfig.json -> npx tsc --noEmit, npx eslint <changed files>.ruff check <path>, mypy <path>, pytest <specific test file>.mvn -q -pl <module> compile, then the single relevant test class via -Dtest=<ClassName>../gradlew :<module>:compileJava / :<module>:test --tests <ClassName>.NO_COLOR=1, --no-color, or --no-colors.completed once its verification command passes.test cases passed, vs 10 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.