zk-data-agent/skills/verify/SKILL.md

name, description, when_to_use, allowed_tools

name	description	when_to_use	allowed_tools
verify	Verify a code change works by running the app and tests.	When the user asks to verify, test, or check that recent changes work.	read_file, bash, grep_search, glob_search

Verify that the recent code changes work correctly.

Instructions

1. Identify what was changed by checking git diff and git status.
2. Determine the appropriate verification strategy:
   • Unit tests: run existing tests and check for failures.
   • Integration tests: run broader test suites if available.
   • Manual verification: start the app/server and test the feature when needed.
3. Run the verification.
4. Report the result clearly:
   • PASS: all checks passed and the feature works as expected.
   • FAIL: describe what failed and why.
   • PARTIAL: some checks passed and some still need attention.

Verification Strategy

• For CLI tools: run the command with test inputs.
• For servers: start the server and make test requests.
• For libraries: run the test suite.
• For config changes: validate that the config loads correctly.