skills.rest
ShaheerKhawaja
ShaheerKhawajaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

productionos-qa-only

Generate a structured QA report with health scores and repro steps.

8|Updated Mar 17, 2026
Search Tags:#automation#workflow#codex#code-quality#qa-report#repro-steps
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-qa-only
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: productionos-qa-only
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/codex-skills/productionos-qa-only
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-qa-only

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a Codex-native wrapper to run the ProductionOS QA pipeline in Codex, producing a structured report with health scores, screenshots, and repro steps but without applying any fixes.

Core Features & Use Cases

  • Codex-native QA wrapper that mirrors the source QA workflow while preserving guardrails and artifacts.
  • Generates a comprehensive QA report including health scores, screenshots, and reproducible steps.
  • Use Case: Validate a codebase's quality and surface issues without automatically modifying code.

Quick Start

Run the productionos-qa-only workflow on your repository to generate a structured QA report with health scores and repro steps.

Frequently Asked Questions about productionos-qa-only

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

FAQPage Schema
How do I generate a QA report for my codebase without applying any fixes?▼

To generate a QA report without applying fixes, run the ProductionOS QA workflow on your repository. It validates codebase quality and surfaces issues with health scores, screenshots, and reproducible steps while preserving source code.

What is a read-only codebase QA validation workflow?▼

A read-only codebase QA validation workflow analyzes your repository's code quality and captures repro steps without modifying the source. It produces a structured report containing health scores and artifacts while strictly enforcing no code changes.

Can I capture reproducible steps and health scores in an automated testing workflow?▼

Yes, you can capture reproducible steps and health scores by running an automated QA workflow. It mirrors the source QA command specification to generate structured reports and screenshots for target-specific testing without applying fixes.

Do I need Codex-native tooling to run a repository-level QA report?▼

Yes, Codex-native tooling is required to run this repository-level QA report generation. The workflow acts as a Codex-native wrapper to preserve guardrails and artifacts defined by the source QA command specification during validation.

What is the best way to validate code quality without automatically modifying code?▼

The best way to validate code quality without modifying code is using a read-only QA wrapper. It executes target-specific testing and surfaces issues in a structured report with health scores and repro steps, ensuring the source-of-truth remains untouched.

Related Skills

Explore More Software Engineering Skills→
8Dionysus8Dionysus
4

aoa-source-of-truth-check

Identify and resolve documentation ambiguity to establish a single source of truth.

Community
Intermediate
jayhjenkinsjayhjenkins

Jay-Dev QA Testing Skill

Automate three-tier QA testing with TEST_INDEX.md and RUNS/ reports.

Community
Intermediate
webdevtodayjasonwebdevtodayjason

dogfood

Automate exploratory QA testing of web applications with structured bug reports.

Community
Advanced
0xdeafcafe0xdeafcafe

review-code

Review changed source files for design and structural quality issues.

Community
Advanced