repo-standards-router

Classify repositories and route them to standards branches and verification gates.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/chf3198/devenv-ops --skill repo-standards-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-standards-router
Source: https://github.com/chf3198/devenv-ops/tree/main/skills/repo-standards-router
Command: npx skills add https://github.com/chf3198/devenv-ops --skill repo-standards-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classifies repositories to determine the correct standards stack, guiding branch selection, policy profile, and verification gates to ensure consistent governance across projects.

Core Features & Use Cases

  • Determine app-type and overlays for a repository and route to the appropriate standards branch and verification gates.
  • Emit actionable controls and handoff signals to downstream governance skills (e.g., github-ops-tree-router) when required.
  • Use Case: Standardize governance routing across multiple repos in an organization to enforce consistent security, collaboration, and release practices.

Quick Start

Run the repo-standards-router at session start to classify a repository and route it to the correct standards stack.

Frequently Asked Questions about repo-standards-router

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

FAQPage Schema
How do I route repository standards to enforce consistent governance across projects?

To route repository standards, classify the repository type and detect overlays to select the correct standards branch, policy profile, and verification gates. This ensures consistent governance by emitting actionable controls and handoff signals for downstream execution.

What is repository standards routing and when do I need it for my projects?

Repository standards routing is the process of classifying repositories to determine the correct standards stack, guiding branch selection and verification gates. You need it to enforce consistent security, collaboration, and release practices across multiple repositories in an organization.

How do I apply verification gates and policy profiles to different repository types?

Apply verification gates and policy profiles by detecting the repository type and its overlays, then using that classification to select the correct standards branch. This routing provides explicit outputs including selected branches and gates for governance handoffs.

Does repo-standards-router require any dependencies to classify repositories?

Repo-standards-router does not require any dependencies to classify repositories and route standards. It operates standalone to detect repository types, apply overlays, and emit governance handoff signals to downstream skills when appropriate.

Can I emit governance handoff signals to downstream skills during repository routing?

You can emit governance handoff signals to downstream skills like github-ops-tree-router when required. The router outputs explicit handoff signals alongside selected branches and verification gates to trigger downstream execution for complex governance workflows.

When should I not use automated repository standards routing for governance?

You should avoid automated repository standards routing if your project lacks distinct repository types or overlays to classify, as the routing mechanism relies on detecting these variations to select the correct standards branch and verification gates.