3.2 KiB

Raw Blame History

Skills-Vault Request: Regression Validation Gate Runner

Date: 2026-06-19

Requested supplier repository:

C:\Users\wangq\Documents\Codex\skills-vault

Requesting CCPE artifacts:

agents/agent-specs/ccra-local-reviewer.agent.md
runtimes/hybrid/ccra-local-review.runtime.md

1. Capability Name

regression-validation-gate-runner

2. Product / Runtime Context

Local CCRA review needs a deterministic way to run or verify project-defined regression and validation gates before the Agent judges whether engineering evidence supports a product or lifecycle claim.

The first consumer is The Mindscape of Bro Tsong, but the Skill should remain a generic gate runner driven by a local command manifest.

3. Repeated Action Or Friction Point

Reviewers frequently need to know which checks were run, whether they passed, which files changed, and where logs were stored. Manually copying command output into review material is error-prone.

4. Inputs

Expected input:

project_root: path
gate_manifest_path: path to a JSON/YAML/Markdown command manifest
output_dir: path
mode: dry_run | run

The gate manifest should define:

gate_id
command
working_directory
expected_exit_code
log_file
timeout_seconds
required_before_review

5. Expected Outputs

Write:

gate-run-report.md
gate-run-report.json
logs/<gate-id>.log

The report should include:

commands_declared
commands_run
commands_skipped
exit_codes
pass_fail_status
duration
log_paths
environment_notes
machine_readable_summary

6. Allowed Actions

Read the project-defined gate manifest.
Run only commands explicitly listed in the manifest when mode = run.
Capture stdout/stderr logs.
Write outputs only under output_dir.

7. Forbidden Actions

Do not invent commands.
Do not edit project files.
Do not change expected labels, rules, model cards, or tests.
Do not install dependencies unless a separate user-approved flow exists.
Do not treat passing gates as product acceptance or lifecycle approval.

8. Validation Expectation

The Skill should include tests for:

dry-run manifest parsing
successful command capture
failing command capture
skipped optional gate
missing command field
timeout handling
UTF-8 paths and Chinese filenames

9. Reusability Rationale

Running declared validation gates and recording logs is deterministic automation. Interpreting whether the evidence is sufficient remains a CCRA Agent responsibility.

Example non-CCRA consumers:

skills-vault:
  Run Skill test, fixture, install, and packaging gates before release.

ccpe-system:
  Run declared validation checks before promoting Agent, Runtime, Skill, or template changes.

writing-workbench:
  Run document validation, citation checks, outline checks, or export checks before review.

video-workbench:
  Run script, asset, render, or export validation gates before production handoff.

development repositories:
  Run project test, lint, build, schema, or deployment-readiness gates and capture logs for review.

10. Current Blocked Task

Formal Local CCRA Runtime can operate manually without this Skill, but high-volume review should depend on a reusable gate runner instead of ad hoc terminal commands.

3.2 KiB Raw Blame History