senior-qa
Improve QA Coverage With Test Automation
Teams often miss coverage gaps and repeat manual QA planning work. This skill provides testing guidance, scaffold scripts, and coverage reporting patterns for Claude, Codex, and Claude Code.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "senior-qa" from https://skillstore.io/skills/davila7-senior-qa.md and its manifest at https://skillstore.io/api/skills/davila7-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.
Test it
Using "senior-qa". Review a React checkout flow before launch.
Expected outcome:
- High-risk paths include payment errors, form validation, authentication state, and retry behavior.
- Recommended tests include unit checks for validators, integration checks for cart totals, and E2E checks for successful and failed payment flows.
- Release should wait until negative payment cases and abandoned checkout recovery are covered.
Using "senior-qa". Create a QA plan for a Next.js dashboard migration.
Expected outcome:
- Start with route rendering, data loading, permission boundaries, and responsive layout checks.
- Add automated coverage for dashboard filters, empty states, API failures, and navigation persistence.
- Track readiness with pass rate, known defects, uncovered critical paths, and regression test completion.
Using "senior-qa". Assess whether Node.js API changes are ready for release.
Expected outcome:
- Focus on contract changes, authorization checks, error responses, and backward compatibility.
- Add integration tests for changed endpoints and E2E tests for user workflows that depend on them.
- Block release if auth regressions, data loss paths, or undocumented breaking changes remain.
Security Audit
SafeThe static command and reconnaissance detections are markdown documentation false positives, not executable backtick use or host enumeration. The Python scripts contain explicit report output options, but I found no hidden file modification, credential access, network activity, prompt injection, or malicious intent.
Risk Factors
๐ Filesystem access (3)
โ๏ธ External commands (24)
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.
Copy report link
https://skillstore.io/skills/davila7-senior-qa/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-senior-qa?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-senior-qa?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-senior-qa/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-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
davila7. (2026). senior-qa security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-senior-qa/audits/10BibTeX citation
@techreport{davila7-davila7-senior-qa-2026,
author = {davila7},
title = {senior-qa security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/davila7-senior-qa/audits/10},
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 10)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/davila7-senior-qa/audits/10"
identifiers:
- type: other
value: "skillstore:davila7-senior-qa:audit:10"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
alirezarezvani-senior-qa
2026-08-21
davila7-senior-qa
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Build a Test Strategy
Create a structured QA plan that maps risks, test types, and quality gates for a new feature or release.
Review Coverage Gaps
Inspect an application area and produce a prioritized list of missing unit, integration, and E2E tests.
Prepare Release Quality Checks
Turn manual validation needs into repeatable checks that fit local development and CI workflows.
Try These Prompts
Use senior-qa to create a QA plan for [feature]. Include key risks, manual checks, and the first automated tests to add.
Use senior-qa to review [project path or module]. Identify likely coverage gaps across unit, integration, and E2E testing.
Use senior-qa to design a test automation roadmap for [application]. Prioritize workflows, test layers, tooling, and CI checkpoints.
Use senior-qa to assess release readiness for [release scope]. Report blocking risks, recommended tests, quality metrics, and follow-up actions.
Best Practices
- Start with user risk and business impact before selecting test types.
- Keep automated tests close to the workflow they protect and run them in CI.
- Review coverage metrics with defect history, flaky tests, and release risk.
Avoid
- Do not treat coverage percentage as proof that critical workflows are protected.
- Do not add E2E tests for every small condition when unit or integration tests are clearer.
- Do not run setup, deployment, or file-writing commands without checking the target project first.
Frequently Asked Questions
Does this skill write tests automatically?
Which projects fit this skill best?
Can it analyze real coverage reports?
Does it work with Claude, Codex, and Claude Code?
Will it run commands without approval?
What should I review before using the scripts?
Developer Details
Author
davila7License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
b959ebfd1043a07c0c4378ab94ca4342cb0259f5
Maintenance freshness
7/20/2026
Usage
9 downloads ยท 206 views
File structure
๐ references/
๐ qa_best_practices.md
๐ test_automation_patterns.md
๐ scripts/
๐ coverage_analyzer.py
๐ SKILL.md