skills.rest
rhenretta
rhenrettaCOMMUNITY
Explore all skills by this author →
GitHub

packages-shared-governance

Enforce governance rules and SemVer compliance for TypeScript and Zod schemas.

1|Updated Mar 6, 2026
Search Tags:#type safety#version control#governance#SemVer#RFC process
One-click install
npx skills add https://github.com/rhenretta/ai-hivemind --skill packages-shared-governance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: packages-shared-governance
Source: https://github.com/rhenretta/ai-hivemind/tree/main/.agent/skills/packages-shared-governance
Command: npx skills add https://github.com/rhenretta/ai-hivemind --skill packages-shared-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires zod, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures adherence to shared governance rules and SemVer for type definitions and RFCs in the ai-hivemind monorepo, helping maintain consistency and versioning integrity.

Core Features & Use Cases

  • Governance Rules: Provides rules for type boundary management, schema definitions, and runtime dependency management.
  • Version Bump Guidance: Assists in determining the correct version bump for changes, requiring RFCs for major changes and documenting minor bumps.
  • Quick Start: Implement Zod schemas for cross-boundary types, ensure they are exported in the packages/shared/src directory, and use them in your code for type safety.

Quick Start

To ensure your types follow governance rules, write a Zod schema in the packages/shared/src/types/ directory and derive TypeScript types from it.

Frequently Asked Questions about packages-shared-governance

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

FAQPage Schema
How do I enforce type safety and schema consistency in a monorepo?▼

You manage type consistency by writing Zod schemas in the shared packages directory and deriving TypeScript types from them to enforce governance rules across the monorepo.

When do I need an RFC for a version bump?▼

An RFC is required for major version bumps to shared types, while minor bumps require documentation, ensuring versioning integrity and adherence to governance rules.

Do I need Zod to manage cross-boundary type definitions?▼

Yes, Zod is required for managing cross-boundary type definitions. You write Zod schemas in the shared source directory and derive TypeScript types from them for runtime validation.

What is the best way to handle SemVer compliance for shared packages?▼

Handling SemVer compliance involves following governance rules that require RFCs for major version bumps and documentation for minor changes to shared package types.

How do I create a Zod schema for cross-boundary types?▼

You create a Zod schema by writing it in the shared packages source directory and exporting it, ensuring type safety and governance compliance across the monorepo.

Related Skills

Explore More Software Engineering Skills→
oakossoakoss
14

zod-validation

Validate and parse TypeScript data using Zod schemas.

Official
Intermediate
jenkinsm13jenkinsm13
3

publish

Automate Python package releases by bumping versions, building artifacts, and publishing to PyPI.

Community
Intermediate
YunosukeYoshinoYunosukeYoshino

ty-pro

Enforce Python type safety with Ty across codebases.

Community
Advanced
ultramaxoAIultramaxoAI

typed-service-contracts

Enforce end-to-end type safety for frontend-backend API contracts with Zod and TypeScript.

Official
Advanced