agentleFS
Sign inStart free
OneByJorahOneByJorah/VirtOffice/.agents/skills/release-checklist/SKILL.md

release-checklist

Skill23 starsChanged 15 days agoMITView on GitHub

Prepare and verify a release using release-please, semantic versions, and the published GHCR image. Use when a project is ready to cut a version. Never tag without approval.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the repo is public, make sure the GHCR package visibility is public.

    line 23
  2. Distinctive:

    Create tags or releases by hand, edit the manifest to force a version, or publish without the owner's approval.

    line 28

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

Releases are driven by release-please. Conventional commits on main produce a release PR. Merging that PR creates the tag, the GitHub release, and triggers the Docker publish. Merging is the approval step, so ask the owner first.

Before asking for approval

  • CI is green on main
  • README quick start works from a clean clone
  • Screenshots match the current UI
  • CHANGELOG.md entries in the release PR read well
  • No open security findings (security-scrub clean)

After the owner merges the release PR

  1. Confirm the tag and GitHub release exist: gh release view.
  2. Confirm the Docker workflow succeeded: gh run list --workflow docker.yml --limit 3.
  3. Pull and run the published image: docker run --rm -p 127.0.0.1:8080:8080 ghcr.io/<owner>/<repo>:<version> and check /healthz.
  4. If the repo is public, make sure the GHCR package visibility is public.
  5. Report the release URL and image tags.

Never

Create tags or releases by hand, edit the manifest to force a version, or publish without the owner's approval.

Download now (ZIP)

  • Other versions30 projects use a version of this.

    Word for word · 1

    1. OneByJorah/offivo★ 17100% same

    Edited · 0

    None found.

    Wrote their own version · 29

    1. Donchitos/Claude-Code-Game-Studios★ 27ksame name
    2. maximhq/bifrost★ 9.3ksame name
    3. tsukumijima/KonomiTV★ 1.1ksame name
    4. erikdarlingdata/PerformanceMonitor★ 526same name
    5. nkarasiak/qgis-mcp★ 364same name
    6. pixel-cellar/Claude-Code-Game-Studios★ 324same name
    7. striderZA/OpenCodeGameStudios★ 93same name
    8. tranhieutt/software_development_department★ 71same name
    9. cenconq25/claude-code-app-studio★ 40same name
    10. CoralGame/Claude-Code-Game-Studios★ 19same name

    19 more not listed

    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.

  • Used alongsideProjects with it also use playtest-report, soak-test 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.
    • CoralGameSkill

      playtest-report

      Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

      Also in 12 projects that use this

    • lilangMaxSkill

      soak-test

      Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

      Also in 9 projects that use this

    • lilangMaxSkill

      team-live-ops

      Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

      Also in 9 projects that use this

    • CoralGameSkill

      team-polish

      Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

      Also in 14 projects that use this

    • +4 more from lilangMax
    • +4 more from CoralGame
  • In this repository7 other files it gives its agents.

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