Run risk-aware QA reviews and quality gate decisions for software stories.
npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-qa-felipemaines
Please help me install this Agent Skill. Skill: aiox-qa Source: https://github.com/FelipeMaines/ProjetoWeb/tree/main/.claude/skills/AIOX/agents/qa Command: npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-qa-felipemaines
This Skill helps teams verify story and code quality by producing risk-aware test architecture guidance and actionable quality gate decisions before merges.
Use case: a story is marked ready for review and needs a defensible QA decision; run the review, then produce a gate decision and test strategy that can be executed by the team.
Run a comprehensive review for a story by typing: *review your-story-id.
High-intent search queries and answers about installing and using this skill.
To generate a quality gate decision, run a comprehensive QA review using the story ID. The review validates acceptance criteria, testing approach, and readiness, then outputs a PASS, CONCERNS, FAIL, or WAIVED outcome with rationales for merge confidence.
Requirements traceability in a QA review maps evidence to requirements to ensure all acceptance criteria are verified. This process assesses non-functional requirements and creates risk profiles to prioritize verification efforts before a story is approved.
You validate non-functional requirements by running structured reviews that assess risk and map evidence. Security scans are integrated via automated CodeRabbit scanning, which includes false-positive verification and browser console validation for runtime issues.
Yes, the QA review workflow integrates automated CodeRabbit scanning with self-healing capabilities to address critical issues. It performs security reasoning checks and false-positive verification to ensure accurate quality gate decisions.
Create a risk-aware test strategy by executing a multi-phase story review that validates test architecture and assesses risk profiles. The workflow enforces operational guardrails, updating only the QA Results section to maintain review integrity.
No, the quality gate workflow enforces operational guardrails by updating only the QA Results section of the story document. This ensures structured governance and prevents unintended modifications to other story sections.
GustaPaesReviews software stories and produces quality gate decisions.
Rinzler78Generate a requirements-to-tests traceability matrix with coverage gap analysis.
bromankoAudit Elm code for port safety, JSON decoder validation, and XSS prevention.
bychrisrEnforces quality gates and reviews test architecture for software development projects.
