Push the current branch and all tags to origin, then create a GitHub release using the latest tag and its CHANGELOG.md entry. Use after tag-version to complete a release.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Push the current branch and tags to origin, then create the GitHub release.
Check that a tag exists to publish:
!git describe --tags --abbrev=0 2>/dev/null || echo "no tags found"
If "no tags found" is shown above, stop and tell the user: "No tags found. Run /release-plugin:tag-version first to create a tag before publishing."
git push origin HEAD
If this fails, report the error. Common causes: no remote configured, no upstream branch set. Do not continue if push fails.
git push origin --tags
git describe --tags --abbrev=0
Store this value as $TAG for the next steps.
Read CHANGELOG.md if it exists. Find the section for $TAG — look for a heading matching ## [$TAG] or ## [v$TAG] (versions may or may not include the v prefix in the changelog). Extract the text between that heading and the next ## [ heading. This is the release notes body.
If CHANGELOG.md does not exist or the version section is not found, use the git log since the previous tag as release notes:
git log $(git describe --tags --abbrev=0 $TAG^)..HEAD --oneline --no-merges
gh release create "$TAG" --title "Release $TAG" --notes "$CHANGELOG_CONTENT"
Print the release URL returned by gh release create. Tell the user: "Release $TAG is live at [URL]."
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.