verify-by-execution-skill
Prove code changes by running the broken and fixed scenarios with recorded output.
Prove code changes by running the broken and fixed scenarios with recorded output.
Verify by Execution requires reproducing the problem before changing code and rerunning the exact scenario afterward. Every conclusion includes the command, relevant output, and a pass, fail, hang, or skip result. Its rules also cover full test suites, clean-state checks, both sides of security gates, and unset, empty, valid, or invalid environment variables.
Resource types
Use cases
Platforms
Test mobile and desktop app navigation without routine screenshots.
Capture and decode logic-analyzer signals through natural-language requests.
Capabilities
Public GitHub facts last synced Jul 10, 2026.
Turn one browser exploration into repeatable end-to-end tests.
Query CloudWatch in natural language and investigate AWS incidents from Claude Code.