All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 29,140
- 1,215
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse testing & qa skills
Showing 505–528 of 29,140 skills
- Bead ReviewQA/adversarial audit of bead decomposition for autonomous agent executionVotes: 0GitHub stars: 2
- Battle PlanBefore ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.Votes: 0GitHub stars: 2
- Balls ModeDecomposed reasoning with explicit confidence scoring. Use for complex decisions, debugging failures, and architectural choices where tracking uncertainty prevents wasted effort.Votes: 0GitHub stars: 2
- Backlog WorkflowProject-agnostic workflow guidance for Backlog.md MCP task management. Covers search-first protocol, scope assessment, task creation standards, lifecycle management, and cross-session coordination.Votes: 0GitHub stars: 2
- Background TasksEfficient handling of long-running commands. Use when running tests, builds, or any command that takes more than a few seconds. Prevents token waste from polling.Votes: 0GitHub stars: 2
- Backend Testing執行與除錯 KCardSwap 後端測試（pytest）：支援快速跑全套、只跑 unit/integration、單一檔案或單一測試、失敗重跑、最慢測試統計、coverage 報告，以及 gcs_smoke（RUN_GCS_SMOKE=1）等情境。也包含本機 Poetry 與 Makefile 的推薦指令與注意事項。Votes: 0GitHub stars: 2
- Backend Testing StandardStandard for writing backend unit tests. Enforces using Mock Data and verifying business logic without direct database manipulation. Use this when writing or refactoring backend tests.Votes: 0GitHub stars: 2
- Backend Testing 3Write and review backend tests with JUnit5, MockMvc, and Spring Boot Test. Use for writing controller tests, service tests, and integration tests.Votes: 0GitHub stars: 2
- Backend Testing 2Write comprehensive backend tests including unit tests, integration tests, and API tests. Use when testing REST APIs, database operations, authentication flows, or business logic. Handles Jest, Pytest, Mocha, testing strategies, mocking, and test coverage.Votes: 0GitHub stars: 2
- Backend TesterRun isolated test environments for backend changes, manage test data, and verify API endpoints. Use when testing Python backend changes without interfering with production instances.Votes: 0GitHub stars: 2
- Backend Patterns 9API design, database operations, error handling, and backend architecture patterns. Use when creating APIs, database schemas, or server-side logic.Votes: 0GitHub stars: 2
- Backend Development Feature DevelopmentUse when working with backend development feature developmentVotes: 0GitHub stars: 2
- Backend Development 5Provides specialized guidance for backend development including API design, database interactions, authentication, error handling, and security best practices. Use when working on backend code, API endpoints, server-side logic, database queries, authentication systems, or when the user mentions backend, API, server, or database development.Votes: 0GitHub stars: 2
- Backend Dev Guidelines 1Comprehensive backend development guide for Go/Chi/PostgreSQL with Clean Architecture. Use when creating routes, handlers, services, interfaces, middleware, working with Chi APIs, sqlc database access, JWT authentication, request validation, correlation IDs, or async patterns. Covers layered architecture (routes → handlers → services → database), interface-first development, error handling, observability, testing strategies, and service decomposition patterns.Votes: 0GitHub stars: 2
- Backend 3Use when writing Lambda functions, API routes, Hono handlers, Express routes, serverless endpoints, or backend services. Use when creating API validation with Zod, implementing service layers, or structuring handler code.Votes: 0GitHub stars: 2
- Azure Devops Work Item UpdateUpdate Azure DevOps work items after implementation completion by linking git commits, adding implementation summaries, and updating status to 'Ready for Testing'. Use when completing a task, finishing a user story, after git commit, or updating work item status. Ensures work items reflect actual work done and maintains traceability between code and work items.Votes: 0GitHub stars: 2
- Aztec TestingAssists with testing Aztec smart contracts using the TestEnvironment. Use when writing unit tests, integration tests, or debugging test failures for Aztec contracts.Votes: 0GitHub stars: 2
- Aztec E2e TestingGenerate Jest end-to-end tests for Aztec contracts with real network interaction. Use when writing integration tests, testing contract deployments, or validating full transaction flows.Votes: 0GitHub stars: 2
- AxumAxum (Rust) web framework patterns for production APIs: routers/extractors, state, middleware, error handling, tracing, graceful shutdown, and testingVotes: 0GitHub stars: 2
- Autonomous LongtaskGuide für lange, autonome Entwicklungsaufgaben mit Claude Code. Optimierte Patterns für Multi-Session-Tasks, Sub-Agents, Parallelisierung und Loop-Closing.Votes: 0GitHub stars: 2
- Auto Test RunnerAutomatically run relevant tests after code changesVotes: 0GitHub stars: 2
- Auth ExpertSenior expert in Auth.js v5 (NextAuth), Edge-First authentication and security. Optimized for Next.js 16.1.1 and React 19.2.Votes: 0GitHub stars: 2
- Auditor 1Independent code auditor. Verifies code against a change log without prior context.Votes: 0GitHub stars: 2
- Audit WorldAudit a world for consistency, D&D 5e 2024 rule compliance, broken links, orphaned entities, and connection gaps. Provides detailed reports and can auto-fix issues.Votes: 0GitHub stars: 2