omniroute-contribution

Validates and publishes OmniRoute pull requests through a gated draft-to-ready workflow.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill omniroute-contribution-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omniroute-contribution
Source: https://github.com/alex-jordan547/agent-setup/tree/main/skills/omniroute-contribution
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill omniroute-contribution-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Contributing to the OmniRoute repository involves strict rules around release branches, changelog fragments, draft PR sequencing, and CI verification, and skipping any step can produce broken or rejected pull requests. This Skill enforces the full contribution lifecycle so every PR follows the repository's Golden Path before it is marked ready for review. ## Core Features & Use Cases - Mandatory preflight checks: A bash script verifies the worktree, upstream remote, active release branch, changelog fragment, and local/remote SHA consistency at each lifecycle stage. - Draft-first PR state machine: Enforces a fixed sequence of commit, push, draft PR creation, PR-numbered changelog fragment, and user-confirmed Ready transition. - Fail-closed gates: Blocks publication when release freeze status, focused tests, PR metadata, or user confirmation is unresolved. - Use Case: You fixed a bug in OmniRoute and need to open a PR against the correct release branch. The Skill identifies the highest active release branch, guides the implementation and focused tests, creates the draft PR, adds the matching changelog fragment, and only marks it ready after your explicit confirmation. ## Quick Start Use the omniroute-contribution skill to prepare and publish my current OmniRoute change as a draft pull request against the active release branch.

Frequently Asked Questions about omniroute-contribution

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

FAQPage Schema
How do I create a pull request for the OmniRoute repository?

Run the contribution preflight script in start mode, read the mandatory guidance files, branch from the highest active release branch, then commit and push. Create the PR as a draft, add a PR-numbered changelog fragment, and only mark it ready after user confirmation.

How do I add a changelog fragment to an OmniRoute PR?

Create exactly one file at changelog.d/{features|fixes|maintenance}/<PR-number>-<slug>.md containing a bullet that references the PR link. Never guess the PR number; create the draft PR first, then name the fragment after its actual number.

Which branch should I target for an OmniRoute pull request?

Target the highest active release/v* branch verified from live GitHub state, not inferred from package versions or memory. The preflight script fetches upstream refs and derives the highest numeric release branch, but you must also check for a release-freeze marker.

Why does the contribution preflight script fail before marking a PR ready?

The ready check fails if the worktree is dirty, the branch is not reconciled with the upstream base, the changelog fragment is missing or mismatched, local and remote SHAs differ, or the changelog integrity gate fails. Resolve the reported issue rather than bypassing the gate.

Can I skip the changelog fragment for an OmniRoute change?

Only for changes that genuinely need no fragment, and the reason must be written in the PR description. User-facing behavior changes always require a fragment, and the draft PR sequence still applies in both cases.