qa

Execute structured QA and red-team tests against new features.

Updated Aug 27, 2025
One-click install
npx skills add https://github.com/Andrej1601/HTMLSignage --skill qa-andrej1601
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Andrej1601/HTMLSignage/tree/main/.agents/skills/qa
Command: npx skills add https://github.com/Andrej1601/HTMLSignage --skill qa-andrej1601

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend excessive time manually validating new features and checking for security gaps. This skill provides an automated, repeatable QA workflow that combines functional validation and red-team style reviews to accelerate release quality.

Core Features & Use Cases

  • Structured testing: validates acceptance criteria, edge cases, and regression potential across frontend and backend changes.
  • Security-focused auditing: performs threat-model style checks to identify potential vulnerabilities and insecure defaults.
  • Documentation & reporting: compiles findings with severity, reproducible steps, and recommended fixes for stakeholders.

Quick Start

Begin by loading the latest feature spec and execute a full QA pass to identify defects and security concerns.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA testing and security audits for new features?

Automate QA testing and security audits by executing structured functional validation and red-team tests against feature specs and recent commits. This workflow identifies defects, regression issues, and security vulnerabilities while generating documented reports with severity and recommended fixes.

How do I perform a red-team security audit on recent code changes?

Perform a red-team security audit by applying threat-model style checks to new features and code changes. This process identifies potential vulnerabilities and insecure defaults, ensuring application security and reliability through structured validation of edge cases.

What is the best way to structure regression testing for feature releases?

The best way to structure regression testing is to validate acceptance criteria and edge cases across frontend and backend changes. Using recent commits and feature specs, you can design comprehensive test plans to catch potential regression issues before release.

Can I use automated testing to identify both functional defects and security vulnerabilities?

Yes, automated testing can identify both functional defects and security vulnerabilities by combining structured manual and automated validation with red-team style reviews. This dual approach accelerates release quality by catching both regression bugs and threat-model security concerns.

How do I document bug triage results with severity and reproducible steps?

Document bug triage results by compiling findings with severity levels, reproducible steps, and recommended fixes for stakeholders. This structured reporting ensures development teams have actionable information to resolve defects and security concerns efficiently.

What do I need to run automated QA validation against new features?

To run automated QA validation, you need the latest feature spec and access to recent code changes and commits. Loading this context allows the system to design comprehensive test plans and perform both manual and automated validation checks.