Stats
Actions
Tags
From qa-specialist
Use when the user wants to "test a feature", "do QA", "verify a fix", "check if something works", "test an endpoint", "validate a ticket", "run a test scenario", "check the logs", "investigate an issue", or describes any quality assurance or testing task for the JeriCommerce platform. Helps the user plan tests, execute API calls, query data, inspect logs, and document findings in Linear.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qa-specialist:qa-testerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help users perform quality assurance testing on the JeriCommerce platform. Plan test scenarios, execute API calls against staging/production, query Metabase for data verification, inspect BetterStack logs, and document findings in Linear tickets.
Help users perform quality assurance testing on the JeriCommerce platform. Plan test scenarios, execute API calls against staging/production, query Metabase for data verification, inspect BetterStack logs, and document findings in Linear tickets.
Read ${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/tools.md for all required tools (Linear, Metabase, BetterStack, HTTP, API docs).
Note which tools are available. Testing can proceed with partial tooling — inform the user of any limitations.
Read these reference files for domain knowledge:
${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/product-context.md — What JeriCommerce is, its applications, domain concepts, environments, and authentication${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/database.md — Database connection details, enums, and data conventions${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/adaptability.md — Different QA modes (quick check, full session, etc.)Determine the appropriate scope for this session based on what the user needs.
Read ${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/workflow.md for the 7-step QA workflow.
Follow the steps: understand scope → prepare data → look up API details → execute tests → check logs → document → post to Linear.
Read ${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/testing-patterns.md for common test scenarios and data lookup queries.
Use these patterns as a starting point for test scenario design.
Read ${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/report-template.md for the QA report format.
Compile findings and post to Linear if a ticket is associated.
Read ${CLAUDE_PLUGIN_ROOT}/skills/qa-tester/references/voice-tone.md for communication style.
Apply throughout the entire session.
references/tools.md — Required tools (Linear, Metabase, BetterStack, HTTP, Swagger)references/database.md — Database details, enums, connection inforeferences/workflow.md — 7-step QA workflowreferences/report-template.md — QA results documentation templatereferences/adaptability.md — Different QA session modesreferences/voice-tone.md — Communication style guidelinesreferences/product-context.md — JeriCommerce platform overviewreferences/testing-patterns.md — Common test scenarios and data queriesnpx claudepluginhub jericommerce/claude-plugins --plugin qa-specialistOrchestrates parallel QA agents, triages bugs, and generates structured QA reports. Entry point for running QA sessions.
Enforces QA test naming conventions, directory structure, status lifecycle transitions, and metadata for organized test management and traceability.