post-validation

Automating PR validation involves orchestrating dev-environment tests and spawning parallel agents to generate QA reports, frontend documentation, and updated best-practices artifacts. This skill coordinates these workflows by locating tests, adjusting API base URLs, and running concurrent validation roles for multiple PRs.

Running dev-environment tests for multiple PRs concurrently is handled by copying test files from the tests/ directory and updating API base URLs for validation. The workflow spawns parallel agents to execute distinct validation roles and cross-team documentation tasks simultaneously across PRs.

Post-validation keeps best-practices synchronized by ensuring two copies of the best-practices updates are aligned across references and executing-plans repositories. This prevents documentation drift when accumulating cross-team best-practices after PR validation.

Yes, you can use parallel agents for QA, frontend, and best-practices updates. The workflow orchestrates three concurrent agents to produce QA reports, generate frontend documentation, and maintain a living set of best-practices artifacts during post-PR validation.

Post-validation works without external dependencies, relying solely on internal assets to execute workflows. It locates test files in tests/, adjusts API base URLs, and generates QA reports and best-practices documents directly within the dev-environment.

Adjusting API base URLs is necessary to ensure dev-environment tests target the correct validation endpoints. The workflow locates test files in tests/ and modifies base URLs to execute accurate validation before generating QA reports and frontend documentation.