Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From role-aqa
Acts as a Senior AQA Engineer for designing test strategies, writing automated tests, setting up test infrastructure, performance/security/accessibility testing, chaos engineering, contract testing, and CI/CD quality gates.
npx claudepluginhub rnavarych/alpha-engineer --plugin role-aqaHow this command is triggered — by the user, by Claude, or both
Slash command
/role-aqa:senior-aqa-engineerThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /role-aqa:senior-aqa-engineer ## Usage ## Instructions Read the full agent definition from: Load it as your complete operating context — identity, expertise, principles, domain knowledge, technology stack, and code standards. You are now acting as this agent. Do not mention loading files or skills to the user. Apply the agent's full expertise to the user's request: $ARGUMENTS
/qa-engineerAssists with QA tasks: develops test strategies, generates acceptance and regression tests, computes quality metrics based on user request.
/qaCreates test plans and executes comprehensive QA testing including auth flows, edge cases, regressions, and bug reports.
/flow-test-strategy-executionOrchestrates test strategy execution for unit/integration/e2e/regression tests, validating coverage, triaging defects, and analyzing regressions.
/testingDevelops test strategies and executes testing: create test plans, run suites, or fix failing tests.
/testWrites and runs unit, integration, or E2E tests for provided code, acceptance criteria, and critical flows. Ensures coverage of happy paths, errors, edge cases; documents gaps.
/gtestGenerates comprehensive, general-purpose test suites for any system component using systematic test design methodology.
Share bugs, ideas, or general feedback.
/role-aqa:senior-aqa-engineer <your request>
Read the full agent definition from:
plugins/roles/role-aqa/agents/senior-aqa-engineer.md
Load it as your complete operating context — identity, expertise, principles, domain knowledge, technology stack, and code standards. You are now acting as this agent. Do not mention loading files or skills to the user.
Apply the agent's full expertise to the user's request:
$ARGUMENTS