app-release
Skill2 starsChanged 6 months agoMITView on GitHub
Automates the release process for Skill Lake app, including version bumping, building, packaging, and publishing to GitHub and Homebrew.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- glebis/claude-skillstheir own version, first seen Jul 1, 2026
- JAVICHILEON/claude---Skillstheir own version, first seen Jul 1, 2026
- luochang212/skill-zootheir own version, first seen May 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- glebis/claude-skills★ 410same name
- luochang212/skill-zoo★ 125same name
- JAVICHILEON/claude---Skills★ 0same 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when you need to publish a new version of the Skill Lake application.
- Distinctive: line 12
Check Prerequisites: Ensure you are on the main branch and have no uncommitted changes.
- Very specific: line 13
Determine Version: Ask the user for the new version number (e.g., 1.1.8) if not provided.
- Very specific: line 14
Execute Release: Run the ./release.sh script with the new version as an argument.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
app-release
Use this skill when you need to publish a new version of the Skill Lake application.
Workflow
- Check Prerequisites: Ensure you are on the
mainbranch and have no uncommitted changes. - Determine Version: Ask the user for the new version number (e.g.,
1.1.8) if not provided. - Execute Release: Run the
./release.shscript with the new version as an argument. - Verification: Confirm that the build succeeded, the DMG was created, and the release was pushed to GitHub and the Homebrew tap.
Usage
./release.sh <new_version>Example:
./release.sh 1.1.8Features
- Code Validation: Automatically runs
flutter analyzeand checks formatting before building. - Automated Build: Builds the macOS app in release mode.
- DMG Packaging: Creates a signed DMG package for easy installation.
- Git Automation: Handles version bumping in
pubspec.yaml, commits, tagging, and pushing. - GitHub Integration: Creates or updates a GitHub Release and uploads the DMG.
- Homebrew Sync: Automatically updates the Homebrew Cask in the dedicated tap repository.
- UI Sync: Ensures the version displayed in the "About" dialog matches the released version using
package_info_plus.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

