New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release-Green Validation

by diegosouzapw in diegosouzapw/OmniRoute

Runs or reads a local Release-Green observer for an exact base or PR candidate and separates hard failures, advisory drift and incomplete evidence.

MITAuto-check passedDevOps & Cloud

Install Release-Green Validation

skills CLI
$ npx skills add diegosouzapw/OmniRoute --skill validate-release-green -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install diegosouzapw/OmniRoute validate-release-green --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .claude/skills && cp -r skills-src/config/quality/skill-templates/validate-release-green .claude/skills/validate-release-green && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
validate-release-green
GitHub stars
74k
Token cost
~740 tokens
SKILL.md length
360 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Runs or reads a local Release-Green observer for an exact base or PR candidate and separates hard failures, advisory drift and incomplete evidence.

  • Preflighting a release candidate before full CI
  • SKILL.md covers Select and execute the actual…, Interpret and compare and Handoff
  • Calls npm
  • Deciding whether a failure existed on the base or came with a PR

What it does

A maintainer preflight check. It resolves the current base and candidate SHA, uses an isolated worktree with its own installed dependencies, and runs the observer's quick profile for a partial diagnosis or its broader profile with build, hermetic and JSON options. Output, process receipts and the validator's own exit code are preserved, and the report is read even when the outer job looks green.

Findings are classed as HARD, the blocking class, or DRIFT, a diagnostic bucket, and neither proves causality, so the same requirement is compared on the exact base before blaming a contributor. A passing local profile means only that profile passed; remaining lanes such as Vitest suites, coverage, security, build and package checks are recorded, and full CI acceptance stays a separate requirement.

When your agent uses it

  • Preflighting a release candidate before full CI
  • Deciding whether a failure existed on the base or came with a PR
  • Separating blocking failures from advisory drift
  • Writing up what a local run did and did not cover

Example prompts

  • “Run the release-green observer on the current candidate and summarize the hard failures.”
  • “Did this failure exist on the exact base too? Compare the two.”
  • “Do a quick release-green pass and list which lanes remain unchecked.”

Requirements

  • Node with npm and the repo's check:release-green script
  • An isolated git worktree with installed dependencies

What it can do on your machine

Read from SKILL.md and the folder at commit 8ad6b1c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release-Green Validation loads about 740 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 360 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~740

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from diegosouzapw/OmniRoute at commit 8ad6b1c, republished under its MIT licence (© diegosouzapw). 360 words, ~740 tokens.

Download SKILL.mdSave it as .claude/skills/validate-release-green/SKILL.md (or your agent's skills folder).
name
validate-release-green
description
Run or inspect the local Release-Green observer for an exact base or combined PR candidate, separating hard failures, advisory drift and incomplete evidence. Use for maintainer preflight; full CI acceptance remains a separate requirement.

Validate Release-Green

Read ../_shared/base-green.md before interpreting remote status or attributing a failure. Resolve the current base and candidate SHA; use an isolated worktree. The observer validates that working tree, not an abstract branch name.

Select and execute the actual profile

Inspect scripts/quality/validate-release-green.mjs, its npm entrypoint and the candidate's workflows before choosing flags. On candidates that provide them:

  • npm run check:release-green -- --quick: partial fast diagnosis.
  • npm run check:release-green -- --full-ci --with-build --hermetic --json: the observer's broader static/test/package profile; this is still not a promise of parity with every workflow lane.

The versioned static gate manifest, if present, describes static scan membership, not all observer or admission jobs. Report unmodeled coverage explicitly.

Build in a worktree with physical dependencies, never an external node_modules symlink. Preserve stdout/stderr, process receipts and the validator's own exit. Read the report even when the outer job is green. Missing, contradictory, stale, cancelled or timed-out evidence cannot establish PASS.

Interpret and compare

HARD is the observer's blocking classification; DRIFT is its diagnostic bucket. Neither class alone proves causality. Compare the same requirement on the exact base before calling a defect contributor-introduced. A ratchet classified as advisory locally can still block in the applicable CI workflow.

A green local profile means only that profile passed. Record remaining lanes, including relevant Node/Vitest suites, coverage, security, build, package/boot and external checks. Do not stamp merge-ready or pre-greened based on a focused run, a draft skip, a closed incident or an old head SHA.

Show full SKILL.md (119 more words)Show less

For machine reports, use scripts/ci/release-green-result.mjs when available on the candidate. It checks the observed exit, exact SHA and event/profile; supply the values from the run rather than inventing an exit code. The report verifier does not establish that omitted workflow requirements ran.

Handoff

Report SHA, profile, command, versions, raw log/artifact locations, hard failures, drift, incomplete lanes and causal confidence. Re-query live refs before using the result for a later decision. A full-current observer PASS may resolve its own incident only through the authorized workflow; it cannot close unrelated requirements or authorize a merge, baseline change, release or deployment.

This skill is diagnostic. Implement fixes only when the user requested changes. Keep thresholds, assertions, contributor credit and action boundaries intact.

© diegosouzapw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in config/quality/skill-templates/validate-release-green of diegosouzapw/OmniRoute.

Open the folder on GitHubat commit 8ad6b1c

Compare with similar skills

Release-Green Validation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release-Green Validation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release-Green Validation this skilldiegosouzapw/OmniRoute74k—~740Automated safety check: PassMIT
CI Triageandymai/brepjs114—~3.7kAutomated safety check: PassApache-2.0
Knowledge Engineering Quality And DeliveryechoVic/blade-code180—~1.4kAutomated safety check: PassMIT
Nuxt Modulesxlanex6/nuxt-meilisearch123—~664Automated safety check: PassMIT
Crabbox Remote Test Runneropenclaw/agent-skills1.1k—~3.6kAutomated safety check: PassMIT
ReleaseSma1lboy/rove146—~3.1kAutomated safety check: WarnMIT

Similar skills

  • CI Triage

    andymai/brepjs

    This skill should be used when a brepjs GitHub Actions job is red or behaving oddly on github.com (a remote CI run, not a local pre-commit/pre-push hook) — "CI failed", "ci-pass is failing", "npm ci…

    114 GitHub stars~3.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Knowledge Engineering Quality And Delivery

    echoVic/blade-code

    覆盖 Blade Code 跨测试、构建、资格验证、发布与双语文档的工程质量闭环. An agent skill from echoVic/blade-code.

    180 GitHub stars~1.4k tokensUpdated 10 days ago
    Testing & QAAuto-check passed

  • Nuxt Modules

    xlanex6/nuxt-meilisearch

    A skill your agent uses when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables…

    123 GitHub stars~664 tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed

  • Crabbox Remote Test Runner

    openclaw/agent-skills

    Detects the Crabbox CLI or config in a repository and uses it to run tests and validation on remote runners, with checks before touching secrets or paid infrastructure.

    1.1k GitHub stars~3.6k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Release

    Sma1lboy/rove

    Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, dispatch the…

    146 GitHub stars~3.1k tokensUpdated today
    DevOps & CloudAuto-check: warnings

  • Manor CI Triage

    manor-os/manor-ai

    A skill your agent uses when Manor GitHub Actions, .github/workflows/ci.yml, OSS smoke/regression jobs, web source smoke, frontend build, lint, or public CI failure logs need diagnosis or repair.

    161 GitHub stars~533 tokensUpdated 29 days ago
    DevOps & CloudAuto-check passed

More from diegosouzapw/OmniRoute

All 50 skills in this repo

  • OmniRoute Backup and Sync CLI

    diegosouzapw/OmniRoute

    Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

    74k GitHub stars~948 tokensUpdated today
    Auto-check passed

  • OmniRoute Settings API

    diegosouzapw/OmniRoute

    Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

    74k GitHub starsUsed in 1 repo~3.6k tokens
    Auto-check passed

  • Quality Scan

    diegosouzapw/OmniRoute

    Runs a scoped, read-only quality scan on a repository candidate and reports exact evidence, failures and frozen debt, without treating a static scan as release acceptance.

    74k GitHub stars~748 tokensUpdated today
    Auto-check passed

  • OmniRoute Database Backups

    diegosouzapw/OmniRoute

    Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.

    74k GitHub starsUsed in 1 repo~395 tokens
    Auto-check passed

  • OmniRoute Provider Management

    diegosouzapw/OmniRoute

    Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.

    74k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • OmniRoute LLM Cache

    diegosouzapw/OmniRoute

    Documents OmniRoute's cache endpoints for reading cache statistics and clearing entries, statistics or the reasoning cache, with notes on TTL and similarity settings.

    74k GitHub starsUsed in 1 repo~529 tokens
    Auto-check passed

Works with

Categories

Questions about Release-Green Validation

What does Release-Green Validation do?

Runs or reads a local Release-Green observer for an exact base or PR candidate and separates hard failures, advisory drift and incomplete evidence. A maintainer preflight check. It resolves the current base and candidate SHA, uses an isolated worktree with its own installed dependencies, and runs the observer's quick profile for a partial diagnosis or its broader profile with build, hermetic and JSON options.

When should I use Release-Green Validation?

Release-Green Validation fits situations like: preflighting a release candidate before full CI; deciding whether a failure existed on the base or came with a PR; separating blocking failures from advisory drift; writing up what a local run did and did not cover.

How do I install Release-Green Validation in Claude Code?

Run `npx skills add diegosouzapw/OmniRoute --skill validate-release-green -a claude-code`. Or copy the skill folder (config/quality/skill-templates/validate-release-green in diegosouzapw/OmniRoute) into .claude/skills/validate-release-green in your project. Claude Code loads it when a task matches its description.

How do I install Release-Green Validation in Codex?

Run `npx skills add diegosouzapw/OmniRoute --skill validate-release-green -a codex`. Or copy the skill folder (config/quality/skill-templates/validate-release-green in diegosouzapw/OmniRoute) into .agents/skills/validate-release-green in your project. Codex loads it when a task matches its description.

Can I use Release-Green Validation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add diegosouzapw/OmniRoute --skill validate-release-green -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-release-green, .gemini/skills/validate-release-green, .github/skills/validate-release-green and .opencode/skills/validate-release-green in your project.

What does Release-Green Validation need to run?

Going by SKILL.md and its folder, Release-Green Validation needs the command-line tools its instructions call (npm). Our summary lists: Node with npm and the repo's check:release-green script; An isolated git worktree with installed dependencies.

Does Release-Green Validation access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release-Green Validation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release-Green Validation use?

Release-Green Validation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release-Green Validation use?

About 740 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release-Green Validation?

Skills that share tags, products or a category with Release-Green Validation: CI Triage (andymai/brepjs, 114 stars), Knowledge Engineering Quality And Delivery (echoVic/blade-code, 180 stars), Nuxt Modules (xlanex6/nuxt-meilisearch, 123 stars) and Crabbox Remote Test Runner (openclaw/agent-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release-Green Validation?

diegosouzapw (a GitHub user) maintains it in diegosouzapw/OmniRoute, which has 73,701 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 6, 2026.

Source: diegosouzapw/OmniRoute on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.