problem-quality-pipeline

Detect and automatically fix quality issues in problem statements and test pipelines.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/JunghyunRyu/qa_labs --skill problem-quality-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-quality-pipeline
Source: https://github.com/JunghyunRyu/qa_labs/tree/main/.claude/skills/problem-quality-pipeline
Command: npx skills add https://github.com/JunghyunRyu/qa_labs --skill problem-quality-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Problem Quality Pipeline automates the detection and automatic remediation of quality issues in problem statements and test pipelines. It links the Problem Curator and pytest-problem-reviewer to identify issues, automatically heal them, and re-validate until a clean PASS is achieved.

Core Features & Use Cases

  • Integrated Auto-Heal Workflow: Detects critical issues (e.g., ambiguous contracts, incomplete tests) and applies curator-driven fixes.
  • Iterative Validation Loop: Re-runs reviewer after curator updates to confirm improvements.
  • Supports Multi-Problem Batch Processing: Handles multiple problems with configurable max iterations.

Quick Start

Run the CLI to initialize or progress fixes on a given problem, e.g., /problem-quality FT-E01 or python -m qa_labs.problem_quality --problem FT-E01

Frequently Asked Questions about problem-quality-pipeline

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

FAQPage Schema
How do I automate problem quality validation and remediation?

Problem quality validation is automated by coupling a Problem Curator agent with pytest-problem-reviewer to detect issues and apply automatic fixes. This pipeline orchestrates an iterative validation loop that re-runs the reviewer after curator updates to confirm improvements until a clean PASS is achieved.

What is an iterative improvement pipeline for QA problem statements?

An iterative improvement pipeline for QA problems detects quality issues like ambiguous contracts or incomplete tests and applies curator-driven fixes. It enforces explicit input-output contracts, maintains markdown integrity, and re-validates across multiple iterations until achieving a passing state.

Can I batch process multiple problems with configurable max iterations?

Batch processing multiple problems is supported with configurable max iterations. The pipeline handles multiple QA problems described in the problem space, applying scenario refinement, difficulty templating, and guardrail validation across each problem independently.

How do I generate reports and iteration history for problem quality reviews?

Report generation is handled automatically by the pipeline, producing a final report, iteration history, and pipeline log. These outputs capture the curator-driven fixes, reviewer validation results, and the full progression of the iterative improvement loop.

Does the problem quality pipeline work without external dependencies?

The pipeline operates without external dependencies, relying on its integrated Problem Curator and pytest-problem-reviewer components. It runs via CLI commands to initialize or progress fixes on a given problem, maintaining markdown validation throughout the auto-heal workflow.

When do I need automated guardrail validation for QA problem statements?

Guardrail validation is needed when QA problem statements require enforced explicit contracts for inputs and outputs. The pipeline applies this validation during scenario refinement and difficulty templating to ensure problem quality meets structural and content standards before final approval.