agentleFS
receptronreceptron/mulmoclaude/.claude/skills/release-app/SKILL.md

release-app

Skill388 starsChanged 7 months agoMITView on GitHub

Create a GitHub release for the MulmoClaude app (not npm packages)

  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Confirm branch: Must be on main with a clean working tree

    line 13
  2. Very specific:

    Add a new ## [X.Y.Z] - YYYY-MM-DD section at the top (below the header)

    line 41
  3. Distinctive:

    Follow Keep a Changelog format

    line 42
  4. Distinctive:

    Write concise bullet points — focus on user-visible changes

    line 44
  5. Distinctive:

    If a previous release entry is misattributed (e.g., a package release using an app version), annotate it with "(package release)"

    line 45
  6. Very specific:

    NEVER: use an app-style vX.Y.Z tag for a package-only release.

    line 95
  7. Very specific:

    MUST run date to get today's date — never guess

    line 99
  8. Distinctive:

    MUST update CHANGELOG before tagging

    line 100
  9. Very specific:

    MUST use v prefix for app tags

    line 101
  10. Distinctive:

    MUST add files individually (never git add -A)

    line 102
  11. Distinctive:

    MUST confirm version number with the user before proceeding

    line 103

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

MulmoClaude App Release

This skill creates a GitHub release for the MulmoClaude app (not individual npm packages).

IMPORTANT: App releases use v prefix tags (v0.2.0). Package releases use bare tags (@mulmobridge/cli@0.1.0). Never mix them.

Pre-release Checks

  1. Confirm branch: Must be on main with a clean working tree
    git status
    git branch
  2. Get current version and last release:
    jq -r .version package.json
    gh release list --repo receptron/mulmoclaude --limit 5
  3. Ask the user: What version? (patch / minor / major) and confirm

Steps

  1. Get today's date (MUST run date, never guess):
    date +%Y-%m-%d
  2. Count changes since last app release:
    # Find the last vX.Y.Z tag (not package tags)
    LAST_TAG=$(git tag -l 'v*' --sort=-v:refname | head -1)
    git log --oneline "$LAST_TAG"..HEAD --no-merges | wc -l
    git log --oneline "$LAST_TAG"..HEAD --no-merges | head -30
  3. Update docs/CHANGELOG.md:
    • Add a new ## [X.Y.Z] - YYYY-MM-DD section at the top (below the header)
    • Follow Keep a Changelog format
    • Sections: Highlights, Added, Changed, Fixed, Security, Breaking Changes (only if applicable)
    • Write concise bullet points — focus on user-visible changes
    • If a previous release entry is misattributed (e.g., a package release using an app version), annotate it with "(package release)"
  4. Update package.json version:
    # Edit package.json version field to the new version
  5. Commit version bump (add files individually):
    git add docs/CHANGELOG.md package.json
    git commit -m "chore: bump version to X.Y.Z + update CHANGELOG"
  6. Create git tag (WITH v prefix for app releases):
    git tag vX.Y.Z
    git push origin main --tags
  7. Create GitHub release:
    gh release create vX.Y.Z --repo receptron/mulmoclaude \
      --title "vX.Y.Z — Short Description" \
      --notes "$(cat <<'EOF'
    ## Highlights
    
    ### Feature 1
    Description...
    
    ### Feature 2
    Description...
    
    ## Breaking Changes
    
    - (if any)
    
    ## Full Changelog
    
    See [CHANGELOG.md](https://github.com/receptron/mulmoclaude/blob/main/docs/CHANGELOG.md#xyz---yyyy-mm-dd) for the complete list.
    EOF
    )"

Tag Convention

TypeFormatExample
App releasevX.Y.Zv0.2.0
npm package@scope/name@X.Y.Z@mulmobridge/cli@0.1.1

NEVER use an app-style vX.Y.Z tag for a package-only release. If a previous release used the wrong convention, edit its title to add "(package release)" and correct the next release.

Important Rules

  • MUST run date to get today's date — never guess
  • MUST update CHANGELOG before tagging
  • MUST use v prefix for app tags
  • MUST add files individually (never git add -A)
  • MUST confirm version number with the user before proceeding
  • Notes body MUST use single-quoted heredoc (<<'EOF') — no backslash escaping of backticks

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.