agentleFS
CarriedWorldUniverseCarriedWorldUniverse/nexus/.agents/skills/release/SKILL.md

release

Skill0 starsChanged 35 days agoApache-2.0View on GitHub

How to deploy merged work to dMon and verify it live before calling it done.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run it fresh and complete this turn.

    line 13
  2. Distinctive:

    Read the full output. Check exit code, count failures.

    line 14
  3. Distinctive:

    Only then make the claim — and state it with the evidence.

    line 15
  4. Distinctive:

    Run the real check — the live task, conformance, or the specific behaviour you changed.

    line 24
  5. Very specific:

    Check env.health (pods, PVCs, sqld reachable).

    line 25
  6. Distinctive:

    Only after the live check passes, move the ticket to Done.

    line 27
  7. Distinctive:

    Don't tell the operator it's deployed until you've seen it serving.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “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

Claiming work is complete without verifying it live is not done. Evidence before claims, always.

The gate (before any "it's deployed" claim)

  1. Identify the command/check that proves the claim.
  2. Run it fresh and complete this turn.
  3. Read the full output. Check exit code, count failures.
  4. Only then make the claim — and state it with the evidence. Words like "should", "probably", "seems to" mean you haven't verified. Stop and verify.

Deploy to dMon

  1. On dMon, pull main, build, install to /usr/local/bin/nexus.
  2. kubectl rollout restart the affected workload; wait for the rollout to complete.
  3. Confirm it came up: the broker is listening and aspects reconnect.

Verify live

  1. Run the real check — the live task, conformance, or the specific behaviour you changed.
  2. Check env.health (pods, PVCs, sqld reachable).
  3. For an operator-facing change, dogfood it (or hand the operator the exact steps).
  4. Only after the live check passes, move the ticket to Done.

Rules

  • The dMon redeploy is the integration test. A green CI is not the same as "works on the cluster".
  • Don't tell the operator it's deployed until you've seen it serving.

Download now (ZIP)

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.