e2e-critical-path
Identify and write E2E tests for the most critical user flows (top 3–5) that impact revenue or retention. Use when defining smoke tests or deciding what to…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-29 00:09
Testing & quality
12,857 results
permission-boundary-test
Test that users cannot access others’ resources, covering IDOR, role violations, and ownership checks. Use when validating authorization, access control, or…
test-plan
Write a comprehensive test plan for a feature or system. Use when users want to create a test plan, QA strategy, or testing checklist for a feature, bug fix,…
validate-inputs-first
Validate that function inputs match the expected shape. Use when debugging unexpected behavior, null errors, type issues, or incorrect arguments.
bmad-os-changelog-social
Generate social media announcements for Discord, Twitter/X, Facebook, and LinkedIn from the latest changelog entry. Use when user asks to 'create release…
safe-cleanup
Use to safely clean up stale LOCAL feature branches left behind by the TDD harness once their slices have shipped — both merged branches and abandoned…
tdd-harness
Use whenever the user wants a feature, product, bugfix, or change taken from idea to a reviewable pull request the disciplined test-driven way. This is the…
dogfood
Per-bstack-P11 reflex 7+16 — explicitly trigger the Dogfood Plan + per-stack cookbook + Dogfood Receipt sequence. Auto-detects the tech stack from repo signals…
bdd-unit-test-reviewer
Review existing unit tests against BDD (Behaviour-Driven Development) principles and provide concrete improvement suggestions. Use this skill whenever the user…
matt-code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding…
acceptance
Use only when the user explicitly invokes acceptance.
test-engineer
Write, run, and optimize project test cases (Vitest).
code-reviewer
Use when reviewing current git changes, PRs, commit ranges, skill definition files, architectural adjustments, or security-sensitive code. Covers correctness, security, architecture, SOLID, deletable code, performance, exception handling, and test risks; by default only outputs a review and does not directly modify code. When the user mentions review, code review, PR review, deep review, code review…
ui-validator
Should be used for any visible UI changes, interaction changes, style fixes, responsive adaptation, dark mode adaptation, and browser-side regression verification. It is responsible for verifying the actual rendering result in the real page, rather than only looking at the code. It should be triggered when the user mentions UI validate, screenshot, browser check, responsive, dark mode, or visual regression.
legal-skill-evaluation
Layered quality evaluation tool for legal Skills. Consumes skill-lint's general quality conclusions, then uses three test materials, six general dimensions, scenario fine-tuning, and lawyer taste to evaluate legal output and locate the minimal repair unit. This skill should be used when reviewing, regression-verifying, or release-accepting legal Skills. Do not use it to replace general Skill lint, formal legal opinions, or cross-scenario ranking.
learn-investigate
Investigate questions with hypothesis testing and evidence logging
omniroute-cli-eval
Run and manage OmniRoute eval suites from the CLI — create suites, run benchmarks, watch live results, view scorecards, and compare model performance. Use when…
testing-orcaq
OrcaQ-specific testing guide. Use when asked to run, debug, or write tests for OrcaQ. Covers all bun test:* scripts, fixture profiles, Vitest projects (unit /…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behaviour, before proposing any fixes. Four-phase root-cause protocol with hard 3-attempt circuit…
tdd
Use when implementing any feature or bug fix. Hard gate — no production code without a failing test first. Applies to vitest (apps/web/) and pytest…
skip-test-with-issue
Skip a flaky or broken test with proper issue tracking. Use when asked to skip a test, disable a test, or mark a test as flaky.
django-tdd
Use when testing Django applications with pytest - TDD workflow, pytest-django setup, factory_boy and model-bakery fixtures, DRF API testing, mocking and…
test-case-generator
Use when the user wants comprehensive test coverage across happy path, edge cases, errors, security, and performance. Triggers include "generate tests", "test…
e2e-test
Comprehensive end-to-end testing command. Launches parallel sub-agents to research the codebase (structure, database schema, potential bugs), then uses the…