feature-qa

Validate merged features against specifications with build, test, and lint checks.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/lucascaro/hivesmith --skill feature-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-qa
Source: https://github.com/lucascaro/hivesmith/tree/main/skills/feature-qa
Command: npx skills add https://github.com/lucascaro/hivesmith --skill feature-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the validation and compliance checking of features after integration, ensuring they align with specifications before deployment.

Core Features & Use Cases

  • Specification Compliance: Runs build, test, lint, and acceptance criteria checks to verify feature correctness.
  • Automated Validation: Assesses whether the feature meets success criteria and identifies regressions or non-goals.
  • Use Case: When a feature branch is merged, use this Skill to perform comprehensive QA checks and determine readiness for release.

Quick Start

Invoke the QA skill with the relevant issue number to start the validation process and review the outcome.

Frequently Asked Questions about feature-qa

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

FAQPage Schema
How do I automate feature validation after merging a branch?

Automated feature validation executes build, test, and lint checks against specifications to verify merged branch compliance and assess deployment readiness. It identifies regressions or non-goals to ensure release quality before proceeding.

What is specification compliance checking in QA automation?

Specification compliance checking runs build, test, lint, and acceptance criteria checks to validate feature correctness. It ensures merged features align with defined success criteria and specifications before deployment.

Can I use automated QA checks to determine release readiness for merged features?

Automated QA checks determine release readiness by validating merged features against specifications and executing build, test, and lint checks. The compliance status report indicates whether the feature is ready for deployment.

How do I run acceptance criteria checks on a merged feature branch?

Run acceptance criteria checks by invoking the QA automation with the relevant issue number. It validates the merged feature against specifications and executes build, test, and lint checks to report compliance status.

What is the best way to identify regressions when validating merged code?

The best way to identify regressions is through automated validation that assesses whether merged features meet success criteria. It executes comprehensive checks and identifies non-goals or regressions before deployment.

When do I need to run build and lint checks for feature compliance?

Run build and lint checks for feature compliance when a feature branch is merged. This ensures the integrated code aligns with specifications and passes acceptance criteria before determining deployment readiness.