Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
中文简介正在准备中。当前显示原文说明。
davila7/claude-with-skills132026年5月15日 更新
免费在 GitHub 公开
publish
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.
中文简介正在准备中。当前显示原文说明。
集成工具GitHub
查看安装方法包含的文件（1）
- SKILL.md1.8 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
Push the current branch and tags to origin, then create the GitHub release.
Pre-flight
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."
Step 1: Push the current branch
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.
Step 2: Push all tags
git push origin --tags
Step 3: Get the latest tag
git describe --tags --abbrev=0
Store this value as $TAG for the next steps.
Step 4: Extract the changelog entry
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
Step 5: Create the GitHub release
gh release create "$TAG" --title "Release $TAG" --notes "$CHANGELOG_CONTENT"
Step 6: Report the result
Print the release URL returned by gh release create. Tell the user: "Release $TAG is live at [URL]."
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
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.
中文简介正在准备中。当前显示原文说明。
davila7/claude-with-skills132026年5月15日 更新
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.
中文简介正在准备中。当前显示原文说明。
davila7/claude-with-skills132026年5月15日 更新
Create a git branch named after a GitHub issue.
中文简介正在准备中。当前显示原文说明。
davila7/claude-with-skills132026年5月15日 更新
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
中文简介正在准备中。当前显示原文说明。
davila7/claude-with-skills132026年5月15日 更新
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.
中文简介正在准备中。当前显示原文说明。
davila7/claude-with-skills132026年5月15日 更新