agentleFS
Sign inStart free
LeanMeanCleanAppsLeanMeanCleanApps/CleanModelContextProtocol/.agents/skills/releases/SKILL.md

releases

Skill1 starsChanged 7 days agoMITView on GitHub

The monthly release of the template - the 1st-of-the-month schedule, the Release Check that skips a month with no changes, the Publish job (SBOM, attestation, NuGet push, GitHub release), version numbers, dry runs and out-of-cycle releases. Use when preparing for a release, rehearsing one, releasing out of cycle, or working out why a release did or didn't happen.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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. Distinctive:

    Make sure everything meant for the month is merged and main is green.

    line 32
  2. Distinctive:

    Read the run summary: Release Check says what it compared and whether it would publish.

    line 34
  3. Very specific:

    Use force to release a month with no real change.

    line 43
  4. Distinctive:

    Delete or edit a past release.

    line 44
  5. Distinctive:

    Add a secret or account that a copy of the template would need for its pipeline to pass.

    line 45
  6. Very specific:

    After a real release: the new version is on nuget.org, the GitHub release has the .nupkg and the .spdx.json, and dotnet new update picks it …

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Releases

The rule

The template releases once a month, on the 1st at 09:17 America/Chicago, from main, with everything merged since the last release. A month where nothing outside .github/ changed doesn't release. Nobody publishes by hand: releases only come from the Build Pipeline (ci-pipeline), and only in the LeanMeanCleanApps organisation, so a copy of the template never tries to publish.

WhenWhat runs
The 1st, 09:17 America/ChicagoThe full pipeline on main, then Release Check and Publish
The 2ndThe organisation's project board moves the month's work to Released and closes its milestone
The 15th, 09:17 America/ChicagoMaintenance: Dependabot's grouped pull request and a scheduled build. No release

Versions are the build date and run number, YYYY.MM.DD.<run>, like 2026.12.01.214. Pull request builds add -pr-<number> and never publish. The milestone for a release is named after its date, like 2026.12.01.

Steps

What the pipeline does

  1. Release Check runs after Summary passes. It compares HEAD with the latest GitHub release tag, ignoring .github/. No changes means no release, unless force is set.
  2. Publish downloads the packed template and logs in to NuGet with trusted publishing (NuGet/login, no stored API key). It publishes the Presentation project to build an SPDX bill of materials, attests the package, pushes it to nuget.org and creates the GitHub release with the package, the SBOM and notes generated from the pull request labels (branches-and-pull-requests).
  3. A scheduled release opens its notes with "Monthly release for <month>". A manual one says "Out-of-cycle release".

Before the 1st

  1. Make sure everything meant for the month is merged and main is green.
  2. Rehearse: run Build Pipeline from the Actions page with run: release and dry-run: true. It runs Release Check and Publish, logs in to NuGet and builds the SBOM, but pushes, attests and releases nothing. Dry runs work from any branch.
  3. Read the run summary: Release Check says what it compared and whether it would publish.

An out-of-cycle release

For a fix that can't wait for the 1st, run Build Pipeline on main with run: release, dry-run: false and, only if the change is in .github/ alone, force: true. Give it its own dated milestone on the board.

Don't

  • Push a package to NuGet or create a release by hand. It skips the SBOM, the attestation and the notes.
  • Use force to release a month with no real change. No changes, no release.
  • Delete or edit a past release. Each release stays, so anyone can go back to it.
  • Add a secret or account that a copy of the template would need for its pipeline to pass. Publishing is guarded by the repository owner for that reason.
  • Release from a branch other than main.

Check

  • The dry run's summary shows Release Check with Publish: true and a Publish job that finished.
  • After a real release: the new version is on nuget.org, the GitHub release has the .nupkg and the .spdx.json, and dotnet new update picks it up.

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.

Check your setup, free