Name: senior-qa
Rating: 68 (1 reviews)
Author: alirezarezvani

senior-qa

Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and configures test runners. Use when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is senior-qa in alirezarezvani/claude-skills

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with copy-paste commands and realistic generated examples, but it is weighed down by inlined reference patterns Claude already knows, missing validate-fix-retry feedback loops in batch workflows, and three referenced files that are not present in the bundle.

Suggestions

Move the "Common Patterns Quick Reference" section into a reference file (or trim it to only project-specific conventions) to remove concepts Claude already knows and tighten the body.

Add explicit validate->fix->retry feedback loops to each workflow (e.g., after running generated tests, instruct to fix failures in the stub/component and re-run until green) so batch operations clear the workflow_clarity cap.

Either create the referenced references/testing_strategies.md, references/test_automation_patterns.md, and references/qa_best_practices.md files, or remove the dangling reference table, so progressive disclosure points to real bundle files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete tool usage, but the "Common Patterns Quick Reference" section inlines ~70 lines of concepts Claude already knows (RTL queries, async testing, MSW setup, Playwright locators, coverage thresholds), and commands repeat across Quick Start, Tools Overview, and Workflows, so it sits at "mostly efficient but includes some unnecessary explanation" rather than 4.	3 / 5
Actionability	Provides copy-paste ready commands with concrete flags and realistic generated output (Button.test.tsx, auth fixtures, jest.config.js, CI yaml) covering the common unit/coverage/E2E cases, matching the 5 anchor for fully executable guidance.	5 / 5
Workflow Clarity	Three numbered workflows each include a verify step (run tests, check coverage, compare reports), but none frames an explicit validate -> fix -> retry feedback loop; per the scoring notes, batch operations (mass test/E2E generation) lacking feedback loops cap workflow_clarity at 3.	3 / 5
Progressive Disclosure	Structure and the reference table (with a Use When column) are well signaled, but the three referenced references/*.md files do not exist in the bundle and reference material is inlined in Common Patterns, so it lands at "some structure but could be better organized" rather than 4's "minor organization gaps".	3 / 5
	Total	14 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description that is specific, comprehensive, and clearly scoped to React/Next.js test automation with concrete trigger phrases. It answers both what the skill does and when to use it without vague language or over-claims.

Dimension	Reasoning	Score
Specificity	Lists seven concrete actions ("Generates unit tests, integration tests, and E2E tests", "Scans components to create Jest + React Testing Library test stubs", "analyzes Istanbul/LCOV coverage reports to surface gaps", "scaffolds Playwright test files", "mocks API calls with MSW", "creates test fixtures", "configures test runners") with comprehensive coverage, matching the 5 anchor rather than 4 which implies minor gaps.	5 / 5
Completeness	Explicitly answers both what (seven concrete capabilities) and when ("Use when the user asks to ..." with concrete trigger phrases), matching the 5 anchor precisely; not 4 since the when-clause is explicit and specific.	5 / 5
Trigger Term Quality	Eight natural trigger phrases ("generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", "improve test quality") are exactly what users would say, with good synonym coverage, fitting the 5 anchor.	5 / 5
Distinctiveness Conflict Risk	A clear React/Next.js testing niche anchored to specific tools (Jest, React Testing Library, Playwright, MSW, Istanbul/LCOV) with distinct triggers and minimal conflict risk, matching the 5 anchor; written in third person ("Generates", "Scans") so no voice penalty applies.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 24 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/senior-qa/SKILL.md
Commit: 19392f7

Reviewed: ~10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.