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
- K9i-0/ccpockettheir own version, first seen Nov 1, 2026
- doublej/consult-user-mcptheir own version, first seen Jul 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- K9i-0/ccpocket★ 1.1ksame name
- doublej/consult-user-mcp★ 39same 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 repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- archive-shipped-plansSkill
- e2e-live-dockerSkill
- e2e-live-mediaSkill
- e2e-liveSkill
- e2e-live-wikiSkill
- make-e2e-liveSkill
- publish-mulmoclaudeSkill
- setup-mulmobridge-lineSkill
- setup-mulmoclaudeSkill
- setup-ollama-localSkill
- setup-relaySkill
- setup-wizardSkill
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
- Distinctive: line 13
Confirm branch: Must be on main with a clean working tree
- Very specific: line 41
Add a new ## [X.Y.Z] - YYYY-MM-DD section at the top (below the header)
- Distinctive: line 42
Follow Keep a Changelog format
- Distinctive: line 44
Write concise bullet points — focus on user-visible changes
- Distinctive: line 45
If a previous release entry is misattributed (e.g., a package release using an app version), annotate it with "(package release)"
- Very specific: line 95
NEVER: use an app-style vX.Y.Z tag for a package-only release.
- Very specific: line 99
MUST run date to get today's date — never guess
- Distinctive: line 100
MUST update CHANGELOG before tagging
- Very specific: line 101
MUST use v prefix for app tags
- Distinctive: line 102
MUST add files individually (never git add -A)
- Distinctive: line 103
MUST confirm version number with the user before proceeding
≈ “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.
Files
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
- Confirm branch: Must be on
mainwith a clean working treegit status git branch - Get current version and last release:
jq -r .version package.json gh release list --repo receptron/mulmoclaude --limit 5 - Ask the user: What version? (patch / minor / major) and confirm
Steps
- Get today's date (MUST run
date, never guess):date +%Y-%m-%d - 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 - Update
docs/CHANGELOG.md:- Add a new
## [X.Y.Z] - YYYY-MM-DDsection 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)"
- Add a new
- Update
package.jsonversion:# Edit package.json version field to the new version - 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" - Create git tag (WITH
vprefix for app releases):git tag vX.Y.Z git push origin main --tags - 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
| Type | Format | Example |
| App release | vX.Y.Z | v0.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
dateto get today's date — never guess - MUST update CHANGELOG before tagging
- MUST use
vprefix 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
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
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.

