mallard-release

# mallard release workflow Reference for adding/updating skills, commands, and shipping releases for [mallard](https://github.com/educlopez/mallard). The tool lives at `/Users/eduardocalvolopez/Developer/Personal/mallard` (on Eduardo's machine). ## When to use this skill - "How do I add a skill to mallard?" - "Release a new version of mallard" / "ship mallard" / "tag mallard vX.Y.Z" - "Update mallard" / "bump the mallard version" - Anything that involves editing files under `skills/`, `claude/commands/`, `claude/agents/`, or shipping the change to other team members. ## TL;DR ```bash # 1. Edit the skill/command file # 2. Bump its `version:` in frontmatter (semver, conservative) # 3. Test locally go build -o mallard . ./mallard update # re-link with backup ./mallard registry # confirm new version + ok status # 4. Commit using Conventional Commits, in English git add skills/<name>/ claude/commands/<name>.md git commit -m "feat(skills): add <name>" # or fix:, refactor:, docs:, chore: # 5. Push git push # 6. Tag a release (this is what propagates to the team) git tag vX.Y.Z git push origin vX.Y.Z # GitHub Actions runs goreleaser → publishes binaries + auto-changelog ``` Team members pick it up with: ```bash curl -fsSL https://raw.githubusercontent.com/educlopez/mallard/main/install.sh | bash mallard update ``` ## Adding a new skill 1. Create `skills/<skill-name>/SKILL.md` with frontmatter: ```yaml --- name: <skill-name> ...