ralph-qa

Trigger manual QA validation for RALPH implementations and generate reports.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/doravidan/supreme-ralph --skill ralph-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-qa
Source: https://github.com/doravidan/supreme-ralph/tree/main/templates/global/skills/ralph-qa
Command: npx skills add https://github.com/doravidan/supreme-ralph --skill ralph-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual QA validation for RALPH implementations is a bottleneck during autonomous development. This skill provides a structured process to trigger QA, gather context, and generate reports, reducing drift between PRD expectations and delivered features.

Core Features & Use Cases

  • QA Triggering: Easily start QA validation against the current implementation state.
  • QA History & Reports: Access last QA results and produce detailed QA reports for audits.
  • Guided Validation: Follow predefined steps and checks (PRD presence, config load, QA history) to ensure quality before release.
  • Use Case: QA a new feature implemented by RALPH by running /ralph-qa to verify acceptance criteria and export a QA report.

Quick Start

Run /ralph-qa in your chat or CLI to start a full QA validation on the current codebase. Use /ralph-qa --report to generate a detailed QA report, or /ralph-qa --fix to attempt automatic issue remediation if supported.

Frequently Asked Questions about ralph-qa

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

FAQPage Schema
How do I trigger manual QA validation for autonomous feature development?

Trigger manual QA validation by running the /ralph-qa command in your chat or CLI to start a deterministic process against the current codebase implementation.

What prerequisites are required to run QA validation on RALPH builds?

QA validation requires a prd.json file and optional config files to load context and validate acceptance criteria during the feature development workflow.

Can I generate detailed QA reports for audits after validating a feature?

Generate detailed QA reports by running /ralph-qa --report to access last QA results and export validation outcomes for auditing delivered features.

How does guided QA validation reduce drift between PRD expectations and delivered features?

Guided QA validation reduces drift by following predefined steps including context loading, criteria validation, and result generation to ensure quality before release.

Can I attempt automatic issue remediation if QA validation finds problems?

Attempt automatic issue remediation by running /ralph-qa --fix to resolve validation problems found during the QA execution process if supported.

What limitations exist when validating RALPH implementations manually?

Manual QA validation is limited to current RALPH implementations and requires specific triggers, prd.json presence, and config loading to execute the deterministic validation process.

Related Skills