governance

Coordinates Gate 1 through Gate 7 workflow for Yuzu code changes using prewritten prompts and output contracts.

15|7|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Tr3kkR/Yuzu --skill governance-tr3kkr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance
Source: https://github.com/Tr3kkR/Yuzu/tree/main/.claude/skills/governance
Command: npx skills add https://github.com/Tr3kkR/Yuzu --skill governance-tr3kkr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The governance skill provides a prompt-writing shortcut to run the full Yuzu governance pipeline, pre-composing the prompts and output contracts for each gate so operators can execute multi-stage reviews without manual prompt crafting.

Core Features & Use Cases

  • Orchestrates Gates 1 through 7 of the governance workflow for code changes, including change summaries and parallel agent fan-outs.
  • Ships pre-written prompt preambles and output contracts that standardize agent behavior and auditing.
  • Triggered by user commands such as "/governance <range>" or "full governance" to run on a PR or commit set.

Quick Start

Run the governance workflow by typing /governance <commit-range> (e.g., /governance HEAD~4..HEAD) to execute Gate 1 through Gate 7.

Frequently Asked Questions about governance

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

FAQPage Schema
How do I automate the full code review governance workflow for a pull request?

To automate code review governance, trigger the pipeline using a command like /governance <commit-range> to execute Gates 1 through 7 with pre-composed prompts for consistent auditing.

What is a multi-stage governance pipeline for code changes?

A multi-stage governance pipeline standardizes code reviews across sequential gates. This automation orchestrates Gates 1 through 7 with pre-written prompt preambles to ensure consistent, auditable agent behavior for Yuzu changes.

How do I run a governance pipeline on a specific commit range?

Run the governance pipeline on a commit range by typing /governance <commit-range>, such as /governance HEAD~4..HEAD, to process the changes through the full multi-stage review workflow.

Does the governance workflow work without specifying a commit or PR range?

Yes, the governance workflow applies default behavior when no commit range is provided, allowing you to execute the pipeline end-to-end without explicitly defining the target changes.

Why use prewritten prompts for an automated code review pipeline?

Using prewritten prompts for a code review pipeline standardizes agent behavior and output contracts, eliminating manual prompt crafting and ensuring an auditable process across all governance stages.

Can I use this governance automation for parallel agent fan-outs?

Yes, the governance pipeline orchestrates parallel agent fan-outs during the code change review workflow, coordinating multiple agents simultaneously across the defined governance gates.