Skills senior-qa

📦

senior-qa

Name: senior-qa
Author: alirezarezvani

Content revision r1 Safe ⚙️ External commands📁 Filesystem access

Improve QA Coverage for Web Apps

Modern teams need clear test strategy and practical automation without slowing delivery. This skill helps Claude, Codex, and Claude Code plan tests, review coverage, and scaffold QA workflows.

Supports: Claude Codex Code(CC)

🥈 81 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "senior-qa" from https://skillstore.io/skills/alirezarezvani-senior-qa.md and its manifest at https://skillstore.io/api/skills/alirezarezvani-senior-qa/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/alirezarezvani-senior-qa.md Signed manifest GET /api/skills/alirezarezvani-senior-qa/manifest Signed lockfile GET /api/skills/alirezarezvani-senior-qa/lockfile

Test it

Using "senior-qa". A product team asks for a checkout release QA plan.

Expected outcome:

A prioritized release checklist covering payment flows, validation errors, account states, browser coverage, rollback checks, and final signoff criteria.

Using "senior-qa". A developer asks where to add tests for a new dashboard filter.

Expected outcome:

A coverage map separating pure filter logic, component behavior, API error states, accessibility checks, and one high-value E2E scenario.

Using "senior-qa". An automation engineer asks how to reduce flaky E2E tests.

Expected outcome:

A stabilization plan covering deterministic data, resilient selectors, network waits, isolation rules, retry policy, and ownership for recurring failures.

Security Audit

Safe

v6 • 7/6/2026 Open versioned report

All static findings were adjudicated as false positives after context review. The command and environment hits are markdown examples or JSON audit text, and the filesystem hits are explicit local report-output options. No prompt injection, malicious intent, secret harvesting, or unauthorized execution evidence was found.

Files scanned

1,173

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/alirezarezvani-senior-qa/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/alirezarezvani-senior-qa/security.svg)](https://skillstore.io/skills/alirezarezvani-senior-qa?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/alirezarezvani-senior-qa?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alirezarezvani-senior-qa/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/alirezarezvani-senior-qa.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

alirezarezvani. (2026). senior-qa security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alirezarezvani-senior-qa/audits/6

BibTeX citation

@techreport{alirezarezvani-alirezarezvani-senior-qa-2026,
  author = {alirezarezvani},
  title = {senior-qa security audit report (audit version 6)},
  institution = {Skillstore},
  year = {2026},
  number = {6},
  url = {https://skillstore.io/skills/alirezarezvani-senior-qa/audits/6},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "senior-qa security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
  - name: "alirezarezvani"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/alirezarezvani-senior-qa/audits/6"
identifiers:
  - type: other
    value: "skillstore:alirezarezvani-senior-qa:audit:6"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

alirezarezvani Recommended Current

alirezarezvani-senior-qa

Skillstore Score 81

Evidence Confidence High

Skillstore usage 26

Updated

2026-08-21

davila7

davila7-senior-qa

Skillstore Score 81

Evidence Confidence High

Skillstore usage 10

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan Release Test Strategy

Create a focused test plan for critical paths, regression risks, manual checks, and automation priorities before a release.

Review Component Coverage

Identify missing component, integration, and user-flow tests for a React or Next.js feature branch.

Start E2E Workflow Design

Outline E2E scenarios, test data needs, selectors, and maintenance risks before building Playwright or Cypress tests.

Try These Prompts

Create a QA Checklist

Create a QA checklist for this feature. Include functional checks, edge cases, regression areas, and test data needs.

Map Test Coverage

Review this module and map the important unit, integration, and E2E coverage gaps. Prioritize risks before test volume.

Design Automation Strategy

Design a test automation strategy for this web app. Include layers, ownership, CI expectations, flaky test controls, and reporting.

Audit Release Readiness

Audit release readiness from a senior QA perspective. Assess critical paths, coverage risks, observability, rollback checks, and manual signoff.

Best Practices

Ask for target framework, test runner, and risk areas before producing a test plan.
Treat script output as a starting report, then inspect application code and coverage artifacts.
Prioritize user-visible behavior, critical paths, and regressions over broad but shallow coverage targets.

Avoid

Do not run generated commands against production systems without project owner approval.
Do not assume placeholder script results prove that a project is well tested.
Do not copy environment setup commands without checking local secret handling rules.