agentleFS
alexei-ledalexei-led/ccgram/.claude/skills/releasing/SKILL.md

releasing

Skill288 starsChanged 7 days agoMITView on GitHub

Full release lifecycle — version bump, CHANGELOG, rich release notes, tag, publish. Use when user says "release", "tag and release", "publish version", "cut a release", "new version".

  • Commits and pushes

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use applying-template-updates, authoring-issues-prs 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.
  • pvliesdonkSkill

    applying-template-updates

    Use when asked to work through, apply, resolve or review a template update pull request (the weekly `copier/update` branch opened by the copier-update workflow), after running `copier update --trust` by hand, or when a template update looks like it leaves no room for something this project needs.

    Also in 3 projects that use this

  • pvliesdonkSkill

    authoring-issues-prs

    Use when filing a bug, opening or creating a GitHub issue, drafting an epic or ticket, writing up a finding or review observation worth tracking, sizing a change before coding, or opening a pull request for this repository. Routes the change to the right repo first (library / template / domain), picks the right issue form, sizes the change to one PR, links epic children as native sub-issues, and applies CONTRIBUTING.md before anything is posted.

    Also in 3 projects that use this

  • zpower426Skill

    roadmapping

    Communicate the product evolution timeline and key milestones, balancing long-term goals with short-term delivery.

    Also in 3 projects that use this

  • quocldSkill

    logging-standard

    Use when writing or reviewing code that logs, when creating or changing a logger, request or job correlation, or log redaction, and when the user says "setup log", "setup logger", "thêm log", "chuẩn hoá log", "log bị lộ token", "log quá nhiều", "review log".

    Also in 3 projects that use this

  • MicrosoftSkill

    writing-release-notes

    Generates release notes and changelog entries for the DocumentDB extension for Visual Studio Code, and announces releases on GitHub Discussions. Use when preparing version releases, creating patch update notes, writing changelog entries, documenting new features and fixes, or posting a release or patch release announcement to Discussions. Handles both major/minor versions (new file) and patch updates (append to existing file).

    Also in 3 projects that use this

  • +7 more from pvliesdonk
  • Other versions19 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 19

    1. dipu-bd/lightnovel-crawler★ 2.6ksame name
    2. lncrawl/lightnovel-crawler★ 2.6ksame name
    3. c15t/c15t★ 2ksame name
    4. WeaveMindAI/weft★ 2ksame name
    5. TeamHypersomnia/Hypersomnia★ 1.7ksame name
    6. vuetifyjs/0★ 734same name
    7. jordanhubbard/nanolang★ 629same name
    8. nteract/desktop★ 193same name
    9. nteract/nteract★ 193same name
    10. pvliesdonk/markdown-vault-mcp★ 38same name

    9 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.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run make check — all must pass.

    line 30
  2. Very specific:

    If a semver like 2.4.0 → use it directly

    line 42
  3. Very specific:

    If patch / minor / major → bump the last tag accordingly

    line 43
  4. Distinctive:

    If empty → analyze commits since last tag to suggest:

    line 44
  5. Very specific:

    Only fix/docs/refactor → patch

    line 46
  6. Distinctive:

    Read the FULL diff since the last tag to understand every change:

    line 60

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

Tag and publish a new version with rich, narrative release notes.

Step 1: Pre-flight

Run in parallel:

git branch --show-current          # Must be main
git status --porcelain             # Must be clean
git log origin/main..HEAD --oneline  # Must be empty (all pushed)

If any fail: report and stop.

Run make check — all must pass.

Step 2: Determine Version

Get the last tag:

git describe --tags --abbrev=0

Parse $ARGUMENTS:

  • If a semver like 2.4.0 → use it directly
  • If patch / minor / major → bump the last tag accordingly
  • If empty → analyze commits since last tag to suggest:
    • feat commits → minor
    • Only fix/docs/refactor → patch
    • Breaking changes → major
    • Present suggestion, ask user to confirm

The version is X.Y.Z (no v prefix in display). The git tag is vX.Y.Z.

Step 3: Generate CHANGELOG

git cliff --tag vX.Y.Z --output CHANGELOG.md

Step 4: Craft Release Notes

Read the FULL diff since the last tag to understand every change:

git diff <last-tag>..HEAD -- '*.py' '*.yml' '*.toml'
git log <last-tag>..HEAD --format="%H %s"

Also read any PR descriptions referenced in commits:

gh pr list --state merged --search "is:merged" --limit 20 --json number,title,body

Now write release notes following this structure and style (study existing releases for tone):

Style Rules

  1. Lead with a theme headline — one sentence summarizing what this release is about
    • Feature release: ## Shell Provider — Chat-First Shell Interface via Telegram
    • Bug fix release: ## Bug Fixes & Reliability
    • Mixed: ## Wrap Prompt Mode — Preserve Your Shell Prompt
  2. Explain WHY, not just WHAT — don't just list commit messages. Explain user-facing impact:
    • Bad: - Fix idempotent prompt markers
    • Good: - **Idempotent prompt markers** — guards prevent duplicate marker injection on repeated setup (e.g., after exec bash or profile reload)
  3. Group by theme, not commit type — if 3 fixes all relate to "shell prompt reliability", group them under that heading instead of a flat "### Fixed" list
  4. Include context — before/after examples, tables, config snippets where they help
  5. End with Install / Upgrade block — always include uv tool upgrade ccgram and brew upgrade ccgram
  6. Keep it concise — a patch release with 2 fixes needs 15-20 lines, not 100. Scale depth with change magnitude.
  7. No "Documentation" section — skip changelog/readme commits, they're noise in release notes
  8. Link PRs where available: ([#36](https://github.com/alexei-led/ccgram/pull/36))

Present the draft release notes to the user for review before proceeding.

Step 5: Commit and Tag

git add CHANGELOG.md
git commit -m "docs: update CHANGELOG.md for vX.Y.Z"
git push origin main
git tag vX.Y.Z
git push origin vX.Y.Z

CRITICAL: The CHANGELOG commit message must NOT contain [skip ci] — it kills tag-triggered workflows.

Step 6: Update GitHub Release

Poll until the release exists (CI creates it), then edit with the crafted notes:

# Poll every 15s, up to 5 minutes
gh release view vX.Y.Z --json tagName 2>/dev/null

Once it exists:

gh release edit vX.Y.Z --notes "<crafted release notes>"

Report final status with link to the release.

Notes

  • hatch-vcs generates version from tag: v2.4.0 → PyPI 2.4.0
  • Release workflow: .github/workflows/release.yml (3 jobs: PyPI, Homebrew, GitHub Release)
  • CI uses git-cliff --latest for baseline notes; this skill replaces them with rich notes
  • Re-tag if needed: git tag -d vX.Y.Z && git push origin :refs/tags/vX.Y.Z

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.