release

스타48

포크7

업데이트2026년 7월 14일 19:32

Release a new version of the project.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

mochow13

mochow13/keen-code

다운로드

Release Skill

Target version (required): $ARGUMENTS

Bump versions. Update the version string in both files to the target version:
- cmd/main.go
- npm/package.json
Update CHANGELOG.md.
- Move all entries under [Unreleased] into a new [X.Y.Z] - YYYY-MM-DD section below it.
- Add a new empty [Unreleased] section at the top.
- Check the commit history for any changes that should be included in the release and were missing in the [Unreleased] section.
- Update the comparison links at the bottom of the file.
Run the tests.
```
go test -race ./...
```
Verify the npm wrapper.
```
cd npm && npm pack --dry-run
```
Commit the version bump. Stage only the four changed files and commit:
- cmd/main.go
- npm/package.json
- CHANGELOG.md
Create and push the tag.
```
git tag vX.Y.Z && git push origin main && git push origin vX.Y.Z
```
The tag must match npm/package.json version exactly (e.g. v1.2.3).
Watch the pipelines. Pushing the tag triggers the build and release workflows. Watch them to completion:
```
gh run watch $(gh run list --limit 1 --json databaseId --jq '.[0].databaseId')
```
If a run fails, inspect logs with gh run view <run-id> --log-failed.
Confirm. Once both pipelines succeed, report the tag, commit SHA, and release URL (gh release view vX.Y.Z --web or --json url) to the user.

이 저장소의 다른 Skills

같은 저장소

Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.

Ask focused clarifying questions to resolve ambiguous requirements before planning or implementing work.

Explain code, behavior, architecture, or diffs with concrete references to the relevant files.

Diagnose failing tests, determine whether code or tests are wrong, and make the smallest passing fix.

Refactor existing code while preserving behavior, keeping changes scoped, and verifying with relevant tests.

Review current code changes for bugs, regressions, test gaps, and project-guideline violations.

name	release
description	Release a new version of the project.

Target version (required): $ARGUMENTS

Bump versions. Update the version string in both files to the target version:
- cmd/main.go
- npm/package.json
Update CHANGELOG.md.
- Move all entries under [Unreleased] into a new [X.Y.Z] - YYYY-MM-DD section below it.
- Add a new empty [Unreleased] section at the top.
- Check the commit history for any changes that should be included in the release and were missing in the [Unreleased] section.
- Update the comparison links at the bottom of the file.
Run the tests.
```
go test -race ./...
```
Verify the npm wrapper.
```
cd npm && npm pack --dry-run
```
Commit the version bump. Stage only the four changed files and commit:
- cmd/main.go
- npm/package.json
- CHANGELOG.md
Create and push the tag.
```
git tag vX.Y.Z && git push origin main && git push origin vX.Y.Z
```
The tag must match npm/package.json version exactly (e.g. v1.2.3).
Watch the pipelines. Pushing the tag triggers the build and release workflows. Watch them to completion:
```
gh run watch $(gh run list --limit 1 --json databaseId --jq '.[0].databaseId')
```
If a run fails, inspect logs with gh run view <run-id> --log-failed.
Confirm. Once both pipelines succeed, report the tag, commit SHA, and release URL (gh release view vX.Y.Z --web or --json url) to the user.