agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/OpenShell/.agents/skills/release-openshell/SKILL.md

release-openshell

Skill17k starsChanged 18 days agoApache-2.0View on GitHub

Pick the latest qualified OpenShell prerelease and tag its commit as stable. Create and qualify a prerelease first when none exists.

  • Reads credentials

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the support branch instead of main for a previous minor version.

    line 18
  2. Very specific:

    If no prerelease exists, agree on the version and source commit, then create and push vX.Y.Z-pre.1.

    line 34
  3. Distinctive:

    Wait for the entire Pre-release run to pass before promoting it.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Release OpenShell

For the intended release version and branch, inspect the latest passing prerelease and changes since the previous stable release. Present the candidate to the maintainer. Once approved, dispatch Release from that branch:

gh workflow run release.yml --ref main -f tag=vX.Y.Z

Use the support branch instead of main for a previous minor version. Release selects the highest-numbered vX.Y.Z-pre.N reachable from that branch with a successful Pre-release run triggered by that tag or dispatched on the same branch, and matching passing release-tag-v1 qualification evidence. Missing or expired evidence blocks promotion. Inspect the selected candidate in the promotion job summary. The entire Pre-release run must succeed, including publication. If qualification passed but publication failed, rerun the failed jobs before promoting the candidate.

Release creates vX.Y.Z at that exact commit, then rebuilds and publishes all stable artifacts without rerunning qualification. Embedded versions change, so stable artifacts are not byte-identical to the qualified prerelease. An existing stable tag may be retried only if it already points to the selected commit. Stable images are saved as OCI archives during the build and pushed under the stable version tags during publication. Their SBOMs are verified before updating latest; the qualified prerelease's commit-SHA image tags remain unchanged.

If no prerelease exists, agree on the version and source commit, then create and push vX.Y.Z-pre.1. Prerelease tag pushes start Pre-release. If the tag was created using GITHUB_TOKEN, dispatch Pre-release explicitly on the intended branch:

gh workflow run release-prerelease.yml --ref main -f tag=vX.Y.Z-pre.1

Wait for the entire Pre-release run to pass before promoting it. Stable tag pushes do not start Release. Release Auto-Tag creates and dispatches prereleases on main.

Stable releases serialize across branches. A release older than the highest stable Git tag publishes versioned artifacts without moving GHCR latest, the GitHub latest release, npm latest, or snap latest/stable. Its npm package uses release-X.Y; snap files remain available in its GitHub Release rather than updating a Snap Store support track. Docs retain an immutable version and advance latest only for a newer version.

Watch the stable release run and report its result.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about NVIDIA/OpenShell

The biggest 5 of 77 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 77

Talked about on Bluesky, YouTube, the web and Hacker News (77 times).

On Bluesky · 41

36 more on Bluesky

On YouTube · 25

20 more on YouTube

On the web · 6

1 more on the web

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free