yuzu-proto

Synchronize canonical Yuzu protobuf sources with gateway mirrors and validate with buf lint.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical protobuf sources for Yuzu drift and misalignment with gateway mirrors; this Skill ensures alignment and safe evolution of proto contracts.

Core Features & Use Cases

  • Treat proto/yuzu/** as the canonical source of truth and keep gateway/priv/proto/** mirrors aligned.
  • Synchronize changes across the repo, including proto/meson.build and codegen scripts, with validation steps.
  • Use to manage safe upgrades of protobuf definitions and ensure consistent code generation across deployments.

Quick Start

Edit proto/yuzu/** and gateway/priv/proto/**, then run the repository's proto sync workflow to propagate changes.

Frequently Asked Questions about yuzu-proto

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

FAQPage Schema
How do I keep protobuf sources synchronized with gateway mirrors to prevent contract drift?

To prevent protobuf contract drift, edit the canonical proto files first and propagate changes to gateway mirrors, then validate with buf lint and breaking proto checks before rebuilding artifacts.

What is the correct workflow for updating protobuf definitions and code generation scripts?

The correct protobuf update workflow involves editing proto/yuzu/** and gateway/priv/proto/**, propagating changes to gen_proto.py and meson.build scripts, and validating with buf lint before rebuilding affected artifacts.

Why do my protobuf gateway mirrors drift out of sync with the canonical sources?

Gateway mirrors drift from canonical sources when proto files are edited independently without propagating changes across the repository and running validation checks to ensure alignment.

Can I use buf lint and breaking proto checks to validate protobuf contract changes before rebuilding?

Yes, buf lint and breaking proto checks are required validation steps after editing canonical proto files and propagating changes to gateway mirrors, ensuring safe evolution before rebuilding affected artifacts.

What's the best way to manage safe upgrades of protobuf definitions across deployments?

The best way to manage safe protobuf upgrades is to treat proto/yuzu/** as the canonical source, synchronize gateway/priv/proto/** mirrors, and validate with buf lint and breaking proto checks to ensure consistent code generation.

Do I need to edit canonical proto files first before updating gateway mirrors and build scripts?

Yes, you must edit the canonical proto files first, then propagate changes to gateway/priv/proto/** mirrors and related build scripts like gen_proto.py, validating with buf lint before rebuilding artifacts.