Menu

Individual skill

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.

agentscope-examples/agents/agentscope-codingagent/src/main/resources/workspace-templates/skills/verify-changes/SKILL.md

Read pinned source

Source commit 55013a429380e91f8b498a31d0e948b38af1e7c1

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
6,286
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Verify Changes

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.

## Procedure

1. Detect the project's check commands from its config files:
   - Node/TS: `package.json` scripts (`build`, `lint`, `typecheck`), `tsconfig.json` -> `npx tsc --noEmit`, `npx eslint <changed files>`.
   - Python: `ruff check <path>`, `mypy <path>`, `pytest <specific test file>`.
   - Java/Maven: `mvn -q -pl <module> compile`, then the single relevant test class via `-Dtest=<ClassName>`.
   - Gradle: `./gradlew :<module>:compileJava` / `:<module>:test --tests <ClassName>`.
2. Run ONLY the checks and tests directly related to the files you changed. Never run the
   full test suite.