QAS Agent (Quality Assurance & Security)

Generate QA test plans, coverage matrices, and unit, integration, E2E, and security tests.

1|Updated Jul 8, 2016
One-click install
npx skills add https://github.com/oehm-smith/linux-env --skill qas-agent-quality-assurance-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: QAS Agent (Quality Assurance & Security)
Source: https://github.com/oehm-smith/linux-env/tree/main/HOME/.claude/skills/lifecycle/testing/acceptance_testing
Command: npx skills add https://github.com/oehm-smith/linux-env --skill qas-agent-quality-assurance-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates software implementations by orchestrating unit, integration, E2E, and security tests across the development lifecycle, reducing manual QA toil and increasing release confidence.

Core Features & Use Cases

  • Structured test planning that maps feature documentation to acceptance criteria.
  • Supports unit, integration, E2E, and security tests, with a guided workflow from planning to execution.
  • Produces a test coverage matrix to monitor risk and ensure test completeness.
  • Use Case: Before PR, generate a comprehensive plan and suites to validate criteria and security requirements.

Quick Start

Provide a complete QA plan by reading feature docs, generate a test plan and coverage matrix, then author unit, integration, E2E, and security tests.

Frequently Asked Questions about QAS Agent (Quality Assurance & Security)

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

FAQPage Schema
How do I automate QA test planning and map acceptance criteria to test coverage?

To automate QA test planning, this Skill reads your feature documentation and generates a structured test plan that maps defined acceptance criteria to a coverage matrix. It produces a guided workflow outlining unit, integration, E2E, and security test steps.

What is the best way to generate unit, integration, and E2E test suites from feature docs?

Generating test suites from feature docs is handled by orchestrating a guided workflow from planning to execution. The Skill authors unit, integration, and E2E tests based on your feature documentation to validate software implementations comprehensively.

Can I include security tests alongside unit and integration testing before a pull request?

Yes, you can include security tests alongside unit and integration tests before a pull request. The Skill automates the creation and execution of comprehensive QA tests across unit, integration, E2E, and security domains to increase release confidence.

How does a test coverage matrix monitor risk and ensure test completeness?

A test coverage matrix monitors risk by mapping defined acceptance criteria directly to generated test suites. The Skill produces this matrix to ensure test completeness across unit, integration, E2E, and security domains, reducing manual QA toil.

Do I need defined acceptance criteria to run automated security and QA tests?

Yes, you need defined acceptance criteria and feature documentation to run automated security and QA tests. The Skill applies to software projects ready for validation where these criteria are defined, guiding test planning and execution.

Why does manual QA toil increase release risk and how does test automation help?

Manual QA toil increases release risk by allowing incomplete validation across software layers. Test automation helps by orchestrating unit, integration, E2E, and security tests, generating a coverage matrix to monitor risk and increase release confidence.