prk-psv-revise

Regenerate failed PSV samples by applying QA feedback and triggering automatic re-validation.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/promptranks/prk-psv-flow --skill prk-psv-revise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prk-psv-revise
Source: https://github.com/promptranks/prk-psv-flow/tree/main/plugins/prk-psv-flow/skills/prk-psv-revise
Command: npx skills add https://github.com/promptranks/prk-psv-flow --skill prk-psv-revise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PSV samples that fail validation require manual rework and QA iteration; this skill automates regenerating and revalidating revisions based on QA feedback.

Core Features & Use Cases

  • Automates revision by reading updated QA feedback and applying fixes
  • Re-validates revised samples automatically
  • Preserves metadata and supports batch processing

Quick Start

Run the PSV revision to fix failed samples using the latest QA feedback and revalidation.

Frequently Asked Questions about prk-psv-revise

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

FAQPage Schema
How do I automate PSV sample revision after QA validation failures?

Automate PSV sample revision by reading updated QA feedback, applying targeted fixes, and triggering automatic re-validation to replace failed entries without manual rework.

What is the best way to apply QA feedback to a failed YAML batch?

Applying QA feedback to a YAML batch involves extracting issues from the original file, applying fixes to the failed PSV samples, and replacing revised entries while preserving metadata.

Can I process batch-level updates for PSV samples marked as REVISED?

Yes, batch-level updates apply to QA batches marked REVISED, enabling end-to-end revision across samples while maintaining original metadata and triggering automatic re-validation.

Do I need the original YAML batch to extract issues and regenerate PSV samples?

Yes, extracting issues and regenerating PSV samples requires access to the original YAML batch and the PSV generation tooling to apply fixes and replace revised entries accurately.

Why does automatic re-validation fail when processing revised PSV samples?

Automatic re-validation of revised PSV samples fails when the QA feedback is not properly extracted from the YAML batch or when the revision workflow cannot access the required PSV generation tooling.

Does the PSV revision workflow preserve metadata during batch processing?

Yes, the PSV revision workflow preserves metadata during batch processing, ensuring that applying QA feedback and replacing revised entries does not alter the original sample attributes.