nexus2-qa

Audit software stories and run critical path smoke tests.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/tcfialho/Herald.Ai.Skills --skill nexus2-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexus2-qa
Source: https://github.com/tcfialho/Herald.Ai.Skills/tree/main/skills/nexus2/nexus_qa
Command: npx skills add https://github.com/tcfialho/Herald.Ai.Skills --skill nexus2-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill consolidates QA processes into a single batch audit, enabling automated validation of software stories to ensure quality and compliance.

Core Features & Use Cases

  • Automated story validation: Executes batch audits over all stories in QA status to verify adherence to acceptance criteria, coverage, and architecture gates.
  • Application lifecycle integration: Manages bringing up the application, running end-to-end smoke tests for critical paths, and tearing down after validation.
  • Use Case: During a software release, run this Skill to autonomously check all stories, perform critical path smoke tests, and update story statuses based on outcomes.

Quick Start

Invoke the QA audit process to validate all stories in QA status, running automated checks and critical path smoke tests against the current build.

Frequently Asked Questions about nexus2-qa

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

FAQPage Schema
How do I automate QA audits for software stories in CI/CD?

Automated QA audits validate software stories in QA status by executing batch checks for adherence to acceptance criteria, coverage, and architecture gates within your CI/CD pipeline. This ensures consistent quality validation and compliance before release.

What is automated story validation and how does it work?

Automated story validation executes batch audits over all stories in QA status to verify adherence to acceptance criteria, coverage, and architecture gates. It operates within development workflows to ensure consistent, reliable QA processes and reports outcomes.

Can I run critical path smoke tests automatically during a software release?

Yes, you can run critical path smoke tests during a software release. The process manages bringing up the application, executing end-to-end smoke tests for critical paths, and tearing down after validation to ensure application stability.

How do I verify story coverage and architecture conformance in my build?

Verify story coverage and architecture conformance by invoking a batch QA audit process against your current build. This executes automated checks and critical path smoke tests to validate all stories and update statuses based on outcomes.

Does automated testing handle application lifecycle setup and teardown?

Yes, automated testing handles application lifecycle integration by bringing up the application, executing end-to-end smoke tests for critical paths, and tearing down after validation. This ensures application stability without manual intervention.