Jeri - QA Tester

Automates QA workflows by validating fixes and posting Fleet-compatible results to Slack.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/JeriCommerce/claude-plugins --skill jeri-qa-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Jeri - QA Tester
Source: https://github.com/JeriCommerce/claude-plugins/tree/main/plugins/qa-specialist/skills/qa-tester
Command: npx skills add https://github.com/JeriCommerce/claude-plugins --skill jeri-qa-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps engineers and QA professionals remove uncertainty when validating features, endpoints, and bug fixes by providing a structured workflow to plan tests, run API calls, verify database state, inspect logs, and compile actionable findings.

Core Features & Use Cases

  • Ticket-driven QA: Fetch Linear ticket context, derive test scenarios, and document results back to the ticket.
  • API and data verification: Dynamically fetch OpenAPI specs, execute API calls with WebFetch or curl, and validate state changes via Metabase queries.
  • Log inspection and evidence collection: Query BetterStack for relevant telemetry, collect evidence, and attach findings to Linear issues.
  • Use Case: Validate a staging bugfix by reproducing the issue via API, confirming database changes, checking logs for errors, and posting a QA summary to the related Linear ticket.

Quick Start

Ask the QA Tester to run tests for a Linear ticket on staging, fetch the ticket, prepare test data, run API calls and Metabase queries, inspect BetterStack logs, and compile a QA summary.

Frequently Asked Questions about Jeri - QA Tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run end-to-end QA testing for an API endpoint using Linear tickets?

Run end-to-end QA testing for an API endpoint by fetching Linear ticket context, executing API calls with WebFetch or curl, verifying database state via Metabase, and inspecting BetterStack logs to compile a QA summary.

What's the best way to validate a staging bugfix across APIs, databases, and logs?

Validate a staging bugfix by reproducing the issue via API calls, confirming database changes through Metabase queries, checking BetterStack logs for errors, and posting a structured QA summary back to the related Linear ticket.

Can I execute API calls and database verification in production environments?

You can execute API calls and database verification in production, but the system defaults to staging and requires explicit confirmation before performing any production write operations to prevent accidental data modification.

How do I fetch OpenAPI specs and run API testing dynamically?

Fetch OpenAPI specs dynamically to define endpoint checks, then run API testing using WebFetch for HTTP requests or Bash and curl for direct API calls, validating state changes against expected responses.

How does log inspection and evidence collection work with BetterStack?

Log inspection with BetterStack involves querying relevant telemetry for errors during test execution, collecting evidence of log anomalies, and attaching the compiled findings directly to Linear issues for ticket validation.