Testing & Quality skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
qa/test-strategy
测试策略和测试金字塔原则，定义单元测试、集成测试、E2E测试的分布和覆盖要求
polylith-check
Validate a Polylith workspace with `poly check` — the canonical CI gate. Verifies brick imports against project `pyproject.toml`s, third-party library declarations vs. the lock file, and (under `--strict`) cross-project version consistency. Exits 1 on failure. Use when the user wants to lint, validate, verify, or CI-gate a Polylith workspace.
polylith-migrate-detect-circular-imports
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Detect and report circular imports introduced by the namespace migration.
polylith-migrate-refactor-tests
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Restructure unit tests to align with the workspace's Polylith theme.
polylith-migrate-verify-stability
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Verify that the migration did not break the project by running test discovery, checking for circular imports, and ensuring the compatibility shim covers all necessary symbols.
polylith-testing
List Polylith bricks and projects affected by **test-code** changes since a git tag using `poly test diff`. Use for selective test runs in CI ("which tests do I need to run?"). For implementation-code diffs, use `polylith-diff` instead.
azd-preflight
**WORKFLOW SKILL** — Runs `mage preflight` from `cli/azd/` and auto-fixes failures. Covers linting, formatting, copyright, spelling, build, and tests. Iterates fix-then-rerun cycles until all checks pass. INVOKES: mage CLI, go CLI, golangci-lint, cspell, bash/sh, ask_user. USE FOR: azd preflight, run preflight, preflight checks, pre-commit checks, azd lint, azd build and test, validate azd changes, check azd code quality, mage preflight. DO NOT USE FOR: deploying azd (use azure-deploy), changelog (use changelog-generation), creating PRs (use pull-request), running only unit tests without the full suite.
Bug Investigation
Systematic bug investigation and root cause analysis