Loading...
Loading...
Found 49 Skills
Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership.
Use when user asks to "validate delivery", "check readiness", or "verify completion". Runs tests, build, and requirement checks with pass/fail instructions.
Test execution patterns, failure classification, and result analysis
Run tests according to repository guidelines. Use after linting passes, before staging changes.
Smoke test for alicloud-media-live. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-content-aimiaobi. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-translation-anytrans. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-search-opensearch. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-backup-bdrc. Validate minimal authentication, API reachability, and one read-only query path.
Runs .NET tests with dotnet test. Use when user says "run tests", "execute tests", "dotnet test", "test filter", "tests not running", or needs to detect the test platform (VSTest or Microsoft.Testing.Platform), identify the test framework, apply test filters, or troubleshoot test execution failures. Covers MSTest, xUnit, NUnit, and TUnit across both VSTest and MTP platforms. DO NOT USE FOR: writing or generating test code, CI/CD pipeline configuration, or debugging failing test logic.
Executes the project's test suite, analyzes failures, and provides fix recommendations.
Verify your own completed code changes using the repo's existing infrastructure and an independent evaluator context. Use after implementing a change when you need to run unit or integration tests, check build or lint gates, prove the real surface works with evidence, and challenge the changed code for clarity, deduplication, and maintainability. If the repo is not verifiable yet, hand off to `agent-readiness`; if you are reviewing someone else's code, use `review`.