post-start-validation

Detect repository changes and run configured governance gates after tasks.

11|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/ruah-dev/ruah-orch --skill post-start-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-start-validation
Source: https://github.com/ruah-dev/ruah-orch/tree/main/.claude/skills/post-start-validation
Command: npx skills add https://github.com/ruah-dev/ruah-orch --skill post-start-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that changes produced by a task are discovered, validated against project governance, optionally auto-fixed, and durably recorded so merges and deployments are safe and auditable.

Core Features & Use Cases

  • Change discovery & classification: Detects modified files, classifies scope (frontend, backend, infra, docs), and selects which gates to run.
  • Governance-driven gates: Reads .claude/governance.md and member governance files, executes annotated gates in order, and respects mandatory/optional/advisory semantics.
  • Bounded auto-fix & safety: Attempts automatic fixes for lint/format issues with bounded retries, writes gate sentinels, and captures session state for warm starts.
  • Knowledge capture & deployment verification: Records what changed, captures decisions and next steps, commits according to governance, and verifies CI/deploy signals.

Quick Start

Run the post-start validation after finishing a task to discover changes, run governance gates with bounded auto-fix attempts, capture session state, and verify deployment status.

Frequently Asked Questions about post-start-validation

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

FAQPage Schema
How do I automate governance checks after a task in a worktree-isolated workflow?

Post-task governance checks are automated by detecting file changes from the repo root, reading .claude/governance.md, and executing annotated gates in order to validate cross-stack consistency for worktree-isolated workflows. Pass/fail results are durably recorded.

What is post-start validation for multi-agent repository changes?

Post-start validation discovers modified files after a task, classifies their scope, and runs configured governance gates with bounded auto-fix attempts. It writes session state and gate sentinels to ensure multi-agent changes are safe and auditable.

How do I run governance gates and capture session state after finishing a task?

Run post-start validation to read .claude/governance.md and member governance files, execute gates respecting mandatory or optional semantics, apply bounded auto-fix retries, and write .claude/.session-state.json for warm starts.

Does post-start validation work with multi-agent and per-task session workflows?

Yes, post-start validation is designed for multi-agent and worktree-isolated workflows with per-task sessions. It uses file scopes and governance annotations to determine which checks to run for each specific task context.

What are the limitations of automatic lint and format fixes during governance checks?

Automatic fixes for lint and format issues are bounded by retry limits to ensure safety. The governance runner respects mandatory, optional, and advisory gate semantics, writing sentinels to indicate pass or fail status for merges and deployments.

Can I capture decisions and verify deployment status automatically after a task?

Yes, post-start validation records what changed, captures decisions and next steps, commits according to governance rules, and verifies CI and deployment signals to ensure changes are safe for deployment.