glowed: Skill for Claude Code

glowed release skill

This skill releases glowed from the main repository and updates the Homebrew tap.

Default inputs

• Version argument: optional.
• If the user provides vX.Y.Z, use that exact tag.
• If the user provides X.Y.Z, normalize it to vX.Y.Z.
• If no version is provided, inspect existing tags and propose the next patch version. If no tags exist, use v0.1.0.

Release safety rules

1. Do not release from a dirty working tree unless the user explicitly asked to include and commit the current changes.
2. Never overwrite an existing git tag without explicit user approval.
3. Run go test ./... before tagging.
4. Confirm gh auth status works before creating GitHub resources.
5. Use the full tap path in user-facing instructions: brew install khw1031/tap/glowed.
6. Keep ignored local files such as .TODO.md, .release/, and bin/ out of commits.
7. Generate and review LLM-drafted changelog notes before tagging.
8. Treat CHANGELOG.md as the public source of truth for release contents; GitHub Release notes should be extracted from it.
9. If a step fails, stop and report the failed command and recovery steps.

Main repository release checklist

From the repository root:

git status --short --ignored
go test ./...
git log -1 --oneline

Determine the release tag:

git tag --list 'v*' --sort=-version:refname | head -10

Generate LLM-drafted changelog notes before tagging. The LLM command must read the prompt from stdin and write Markdown to stdout. If no LLM command is configured, the script writes .release/changelog-prompt-vX.Y.Z.md; ask the user to run their preferred LLM and save the result as .release/notes-vX.Y.Z.md.

# Example with Codex CLI:
scripts/draft-changelog.sh vX.Y.Z --llm-cmd "codex exec --sandbox read-only -"

# Or with an environment-specific command:
GLOWED_CHANGELOG_LLM="YOUR_LLM_COMMAND" scripts/draft-changelog.sh vX.Y.Z

Review and edit the generated notes:

${EDITOR:-vi} .release/notes-vX.Y.Z.md