agentleFS
Sign inStart free
teopostteopost/getpaper/.claude/skills/release/SKILL.md

release

Skill1 starsChanged 16 days agoMITView on GitHub

Publish a new GetPaper release - changelog, version bump, tag, push, public mirror, GitHub release notes in English and Docker image check. Use only when the maintainer asks for a release.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 184 edited versions we read keep these.

  • 2

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

    Update version examples if they mention an older release: README.md, README_ITA.md, docs/index.html, docs/it/index.html, docs/llms.txt.

    line 31
  2. Very specific:

    Run the checks from CLAUDE.md (at least cargo test and docker compose build if disk space allows).

    line 33
  3. Very specific:

    Commit: Release X.Y.Z, then an annotated tag: git tag -a vX.Y.Z -m "GetPaper X.Y.Z".

    line 35
  4. Distinctive:

    Known limitations: if any changed.

    line 60
  5. Distinctive:

    Only verified facts; no em dash.

    line 62

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

Publish version $ARGUMENTS (if empty, propose the next version from the Unreleased changes using Semantic Versioning: until 1.0.0, new features bump the minor version, fixes the patch version). Write everything in English.

1. Preconditions

  • Working tree clean and on main, up to date with origin/main (git status -sb, git fetch origin).
  • git config getpaper.publish.email and git config getpaper.publish.rewrite are set; if not, stop and ask the maintainer for the values (they are local and never committed).
  • Git author identity is set (git config user.name / user.email); if not, ask which identity to use.
  • gh auth status works for the teopost account.
  • The tag vX.Y.Z does not exist yet, locally or on GitHub.
  • The Unreleased section of CHANGELOG.md is not empty. If it is, build it from git log <last tag>..HEAD, describing only changes you can verify in the diff.

2. Prepare the release commit

  1. In CHANGELOG.md, move the Unreleased entries under ## [X.Y.Z] - YYYY-MM-DD (today), leave an empty ## [Unreleased], and update the compare links at the bottom: [Unreleased]: .../compare/vX.Y.Z...HEAD and [X.Y.Z]: .../releases/tag/vX.Y.Z.
  2. Set the version in server/Cargo.toml (version = "X.Y.Z"), server/Cargo.lock (the getpaper package entry) and web/package.json (and the root entries of web/package-lock.json).
  3. Update version examples if they mention an older release: README.md, README_ITA.md, docs/index.html, docs/it/index.html, docs/llms.txt.
  4. Run the checks from CLAUDE.md (at least cargo test and docker compose build if disk space allows). If a check cannot run, say so in the final report.
  5. Commit: Release X.Y.Z, then an annotated tag: git tag -a vX.Y.Z -m "GetPaper X.Y.Z".

3. Push and publish

git push origin main
git push origin vX.Y.Z
make publish                 # pushes main to teopost/getpaper with rewritten emails
git fetch public

The public commit has a different hash. Create the public tag and release on it:

SHA=$(git rev-parse public/main)          # must be the "Release X.Y.Z" commit
gh release create vX.Y.Z -R teopost/getpaper --target "$SHA" \
  --title "GetPaper X.Y.Z" --notes-file <notes.md> --latest

4. Release notes (notes.md, English)

  • One sentence on what the release is about.
  • Upgrade: docker compose pull && docker compose up -d, or pin GETPAPER_IMAGE=ghcr.io/teopost/getpaper:X.Y.Z; call out breaking changes, new required variables and database migrations, and recommend a backup first.
  • Highlights: the user-visible changes from the changelog, grouped (Added, Changed, Fixed).
  • Known limitations if any changed.
  • Link to the full CHANGELOG.md and to the documentation.
  • Only verified facts; no em dash.

5. Verify

  • gh run list -R teopost/getpaper → the "Docker image" run for the tag vX.Y.Z succeeds (gh run watch <id> --exit-status).
  • docker manifest inspect ghcr.io/teopost/getpaper:X.Y.Z lists amd64 and arm64; :X.Y exists too.
  • The release page shows the notes and is marked as latest.
  • The GitHub Pages deployment for the new commit succeeds and https://getpaper.it responds.

Report what was released, the links (release, image), the checks that passed and any that were skipped.

Download now (ZIP)

  • Other versions194 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 194

    1. paperclipai/paperclip★ 110ksame name
    2. modelcontextprotocol/servers★ 92ksame name
    3. remotion-dev/remotion★ 70ksame name
    4. traefik/traefik★ 65ksame name
    5. usememos/memos★ 64ksame name
    6. tw93/Pake★ 63ksame name
    7. Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
    8. Yeachan-Heo/oh-my-claudecode★ 40ksame name
    9. tobi/qmd★ 30ksame name
    10. jlowin/fastmcp★ 28ksame name

    184 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 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

    • MicrosoftSkill

      pr-report

      Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.

      Also in 5 projects that use this

    • Microsoft AzureSkill

      documentation-consistency

      Keeps GPT-RAG MCP service and umbrella documentation aligned with shipped behavior. Use for capabilities, configuration keys, deployment steps, endpoints, defaults, operations, or breaking changes.

      Also in 6 projects that use this

    • parcadeiSkill

      agent-context-isolation

      Agent Context Isolation

      Also in 3 projects that use this

    • +3 more from Grinv
  • In this repository2 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