agentleFS
mavrovdemavrovde/thekotlin.com/.claude/skills/release-flow/SKILL.md

release-flow

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

The sanctioned release procedure for TheKotlin.com — ./release.py, the tag-driven "CI & Deployment" pipeline, and the tagged≠deployed verification rule. Load when preparing, running, or verifying a release, or when asked "is vX.Y.Z out?".

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. tw93/Mole★ 75ksame name
    2. jyje/hermes-agent-helm★ 18same name
    3. JarvusInnovations/agent-skills★ 1same name
    4. daikitigogo/dtg-claude-plugins★ 0same name
    5. pankaj-mahaur/Agent-Daemon★ 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    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. Very specific:

    Never hand-edit version in build.gradle.kts (the pre-push hook blocks it outside chore(release): commits), never raw docker-build for prod.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 5 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 flow — TheKotlin.com

The only release mechanism is ./release.py --patch|--minor|--major (repo root). Never hand-edit version in build.gradle.kts (the pre-push hook blocks it outside chore(release): commits), never raw docker-build for prod.

What release.py does (read it — 90 lines)

  1. python3 manage.py stop — takes down your local compose stack.
  2. Bumps version = "X.Y.Z" in root build.gradle.kts.
  3. git add build.gradle.kts — only the bumped file. (It used to stage a hardcoded, partly stale list; §3 of lessons-learned has the history.) Still run only on an otherwise-clean tree — the release commit should contain the bump and nothing else.
  4. Commits chore(release): vX.Y.Z, tags vX.Y.Z, pushes main + tags.

--patch/--minor/--major is REQUIRED; with no argument the script prints usage and exits 1 without touching anything.

What the tag triggers

.github/workflows/deployment.yml on v*.*.*: backend/frontend/admin CI → Playwright e2e (backend health-gated on /api/stats) → Docker — Build * pushing backend, frontend, admin, nginx images to ghcr.io.

Verification ladder (say only what the rung you reached proves)

  1. Tag pushed → "release initiated".
  2. gh run watch <id> --exit-status green → "images published to ghcr.io".
  3. Live-site check (prod host actually pulled the tag) → only now: "deployed".

Preconditions checklist

  • On main, pulled, working tree clean.
  • All release PRs merged with pr-reviewer APPROVE.
  • Root ./gradlew check green + frontend npm run lint green (lessons-learned §7).
  • SemVer bump chosen BY CONTENT from the merged PRs (major=breaking, minor=new user-facing capability, patch=everything else) — one-line justification.
  • security-triage sweep requested for the release notes.

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.