Loading...
Loading...
Found 37 Skills
Minimal TTS smoke test for Model Studio Qwen TTS.
Minimal validation for crawl-and-skill workflow readiness.
Run git-workspace-review first to understand which tests need updates. Use when updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation. Do not use when auditing test suites - use pensive:test-review. DO NOT use when: writing production code - focus on implementation first.
Generate manual test plans for PR changes with verified commands and pass/fail criteria
Smoke test for alicloud-network-cdn. Validate minimal authentication, API reachability, and one read-only query path.
Add acceptance tests under a functional spec in a ***plain spec file. Use when the user wants to add verification criteria for a specific functional spec, or after adding a functional spec that needs testable success criteria.
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
Evidence-based test debugging enforcing systematic root cause analysis. Use when tests are failing, pytest errors occur, test suite not passing, debugging test failures, or fixing broken tests. Prevents assumption-based fixes by enforcing proper diagnostic sequence. Works with Python (.py), JavaScript/TypeScript (.js/.ts), Go, Rust test files. Supports pytest, jest, vitest, mocha, go test, cargo test, and other frameworks.
Minimal smoke test for SLS log query skill. Validate SDK auth and one bounded query.
Reads documented bugs from bugs.md, analyzes root causes, implements fixes with regression tests, and validates the full test suite. Prioritizes fixes by severity (high to low). Updates bugs.md with correction status and generates a final bugfix report. Use when the user asks to fix bugs, resolve issues, or run the bugfix workflow for a feature. Do not use for new feature implementation, code review, or QA testing.
Smoke test for Alibaba Cloud ALB skill. Validates SDK auth, script compilation, list instances, and health check flows.
Execute coding tasks with a strict delivery workflow: build a full plan, implement one step at a time, run tests continuously, and commit by default after each step (`per_step`). Support explicit commit policy overrides (`final_only`, `milestone`) and optional BDD (Given/When/Then) when users ask for behavior-driven delivery or requirements are unclear.