agentleFS
Sign inStart free
sametbrrsametbrr/github-manager/skills/release-workflow/SKILL.md

release-workflow

Skill0 starsChanged 12 days agoMITView on GitHub

Installs a project-type-aware GitHub Actions release workflow (.github/workflows/release.yml) into a local repo. Detects npm, MCP server, NuGet, Python, Go (plain, GoReleaser or with an npm wrapper), agent plugin, single skill and VERSION-file projects plus the default branch, then tags, publishes to the registry and creates a GitHub release. Use when the user wants automated releases or publishing for a repo. Never commits.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. fxstein/ai-todo★ 16same name
    2. SUDARSHANCHAUDHARI/DroidForge★ 1same name
    3. crux-cli/crux★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run only when the user explicitly asks.

    line 14
  2. Very specific:

    add (default): write release.yml if it doesn't exist.

    line 61
  3. Very specific:

    Private repos: remove --provenance from npm templates.

    line 83
  4. Distinctive:

    Existing publishers: if another workflow already publishes, suggest removing one of them to avoid double publishing.

    line 84
  5. Very specific:

    Write only .github/workflows/release.yml in the target repo.

    line 98
  6. Distinctive:

    Every template refuses to release from anything but the default branch: a manual run must start on it, and a pushed tag must point to a …

    line 102

“Common” is measured: kept by at least 6 in 10 of the 3 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-workflow

Writes .github/workflows/release.yml for one local repo. After the user commits it, the repo releases itself: tag, registry publish where there is one, and a GitHub release with notes.

Run only when the user explicitly asks.

Usage

release-workflow [--repo-dir <path>] [--type <type>] [--branch <name>] [--audit] [--force]

--repo-dir defaults to the current directory. --type and --branch default to detection.

1. Detect

The script lives in this skill's folder, but you run it while the target repo is the working directory. Resolve scripts/add-release-workflow.sh against this skill's directory to an absolute path first and use that ($SCRIPT below).

bash "$SCRIPT" <repo-dir> --detect

Detection order (first match wins):

TypeSignalTriggerPublishes to
goreleasergo.mod + .goreleaser.yamltag push v*GoReleaser (GitHub release + its publishers)
go-npmgo.mod + npm/package.json wrappertag push v*GitHub release binaries + npm wrapper
gogo.modtag push v*GitHub release with 6 cross-compiled binaries + checksums
mcppublic package.json with @modelcontextprotocol/sdk or server.jsonversion bump or tag pushnpm (provenance) + MCP Registry if server.json
npmpublic package.json with a versionversion bump or tag pushnpm (provenance)
plugin.claude-plugin/plugin.jsonbump of its versionGitHub release only; cross-checks .codex-plugin and skills/*/SKILL.md versions
nugetpackable *.csproj<Version> bump or tag pushnuget.org
pythonpyproject.tomlversion bump or tag pushPyPI (trusted publishing)
skillone SKILL.md (root or skills/<name>/)frontmatter version bumpGitHub release only
genericVERSION filechange of VERSIONGitHub release only
npm (private)package.json with "private": trueversion bumpGitHub release only

The release branch is the remote default branch (origin/HEAD), then the current branch, then main. Show the detection output to the user. If nothing is detected, ask for --type or suggest a VERSION file.

2. Mode

  • --audit: no writes. Report whether release.yml exists, whether it matches the detected type, and whether other workflows already publish (the script warns about them). Check existing workflows for unsafe patterns: commit text pasted into run: (for example --notes "${{ steps.x.outputs.notes }}"), hardcoded main on a repo whose default branch differs, publishing without a tag/version check.
  • add (default): write release.yml if it doesn't exist.
  • --force: overwrite the existing file after the user confirms.

Preview first when useful: bash "$SCRIPT" <repo-dir> --stdout.

3. Apply

bash "$SCRIPT" <repo-dir> [--type <type>] [--branch <name>] [--force]

The script writes one file and never commits, pushes or calls the GitHub API.

4. Tell the user what the workflow needs

  • Version field: npm/mcp → package.json version; nuget → <Version>; python → [project] version (dynamic versions: release by tag push); plugin → .claude-plugin/plugin.json version (keep .codex-plugin/plugin.json and every SKILL.md metadata.version equal); skill → frontmatter version; generic → VERSION; Go → tags only.
  • Secrets / publisher setup: npm → NPM_TOKEN or npm trusted publishing; nuget → NUGET_API_KEY; python → a PyPI trusted publisher with environment pypi; MCP Registry → mcpName in package.json and a server.json.
  • Private repos: remove --provenance from npm templates.
  • Existing publishers: if another workflow already publishes, suggest removing one of them to avoid double publishing.

5. Summary

RELEASE-WORKFLOW  <repo>
  type: <type>   branch: <branch>   release.yml: written | skipped | audit
  next: bump the version (or push a tag) after committing the workflow

Rules

  • One local repo per run. Batch installs across remote repos are out of scope.
  • Write only .github/workflows/release.yml in the target repo. Never commit or push without explicit user approval.
  • Templates never paste commit messages into shell commands; notes come from --generate-notes or a notes file.
  • Every template refuses to release from anything but the default branch: a manual run must start on it, and a pushed tag must point to a commit reachable from it.

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