All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 29,138
- 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 457–480 of 29,138 skills
- Bug Health Inline 1Inline orchestration workflow for automated bug detection and fixing. Provides step-by-step phases for bug-hunter detection, priority-based fixing with bug-fixer, and verification cycles.Votes: 0GitHub stars: 2
- Bug FixSystematic workflow for verifying bug fixes to ensure quality and prevent regres...Votes: 0GitHub stars: 2
- Bug Fix TestingPatterns for creating tests that verify bug fixes and prevent regressions. Use when writing tests for bug fixes, creating regression tests, or verifying fix effectiveness.Votes: 0GitHub stars: 2
- Bsblan TestingWrite and run tests for the python-bsblan library. Use this skill when creating unit tests, working with fixtures, or ensuring code coverage requirements are met.Votes: 0GitHub stars: 2
- Bsblan ParametersAdd new BSB-LAN parameters to the python-bsblan library. Use this skill when adding parameter IDs, updating models, or extending the API to support new heating controller parameters.Votes: 0GitHub stars: 2
- Browser VerificationVerify browser-based acceptance criteria using ExecuteAutomation Playwright MCP with multi-tool fallback chain.Votes: 0GitHub stars: 2
- Browser Use E2eGenerate and run E2E tests using browser-use AI automation. This skill should be used when creating automated browser tests, testing authenticated flows, generating test scripts from natural language, or validating user journeys with AI-powered browser control. Handles credentials securely via .env.test with domain-prefixed variables.Votes: 0GitHub stars: 2
- Browser Use 2Browser automation for UI testing, screenshots, and workflow verification. Routes to optimal tool based on context.Votes: 0GitHub stars: 2
- Browser TestingBrowser testing with Playwright MCP for visual and functional validationVotes: 0GitHub stars: 2
- Browser 7Code-first browser automation and web verification. USE WHEN browser, screenshot, navigate, web testing, verify UI, VERIFY phase. Replaces Playwright MCP with 99% token savings.Votes: 0GitHub stars: 2
- BreakdownBreak down epics and features into concrete backlog tasks with dependencies. Use when planning work, decomposing large features, or organizing sprints. Trigger with "break down", "decompose", "plan feature", "create subtasks".Votes: 0GitHub stars: 2
- Brane ShipComplete workflow for verifying and committing Brane SDK changes. Run after implementing fixes/features to verify impact, test affected modules, and prepare for commit.Votes: 0GitHub stars: 2
- Brane ImpactAnalyze change impact and discover affected tests. Use after making changes to understand what depends on the modified code, find relevant tests, and determine what to run.Votes: 0GitHub stars: 2
- Brane Code ReviewReview Brane SDK code for correctness, Java 21 patterns, type safety, and architectural consistency. Use when reviewing PRs, checking code changes, or validating implementations against Brane standards.Votes: 0GitHub stars: 2
- Branch DisciplineEnforce one branch per issue, small focused commits, and clean git history. Use with /branch command.Votes: 0GitHub stars: 2
- Brainstorming ValidatingThe VALIDATING phase runs the completeness gate to ensure design is ready for implementationVotes: 0GitHub stars: 2
- Brainstorming 63Socratic design refinement before implementation. Use when planning creative work or designing features.Votes: 0GitHub stars: 2
- Brainstorming 54Collaborative idea refinement - turns rough ideas into fully-formed designs through questioning, alternative exploration, and incremental validation. Use before writing code or implementation plans.Votes: 0GitHub stars: 2
- Brainstorming 51Use BEFORE any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 2
- Brainstorming 48Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processesVotes: 0GitHub stars: 2
- Brainstorming 47IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validationVotes: 0GitHub stars: 2
- Brainstorming 39You MUST use this, UNLESS the human says otherwise, before any EXTENDED creative work (not simple execution) - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 2
- Brainstorming 37IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validationVotes: 0GitHub stars: 2
- Brainstorming 36IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validationVotes: 0GitHub stars: 2