メニュー
Cut a gocron release — bump AppVersion, align the migration version id, run the full CI check locally, and tag only when everything is green. Use when asked to "release", "发版", "bump version", "cut a release", or "打 tag".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/gocronx-team/gocron --skill releaseコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag. Use when asked to release, 发版, bump the version, cut a release, 打 tag, or assess release readiness.
Implement or review an end-to-end gocron HTTP API change. Use when adding or changing Gin routes, handlers, request or response payloads, authorization, audit behavior, frontend API clients, API types, OpenAPI-style documentation, or API tests.
Create, review, or verify gocron database migrations across SQLite, MySQL, and PostgreSQL. Use when adding or changing GORM models, columns, indexes, constraints, persisted settings, migration version ids, Install tables, upgradeForNNN functions, or migration tests.
SOC 職業分類に基づく
SKILL.md を表示中
| name | release |
| description | Cut a gocron release — bump AppVersion, align the migration version id, run the full CI check locally, and tag only when everything is green. Use when asked to "release", "发版", "bump version", "cut a release", or "打 tag". |
Follow these steps in order. Never tag before the full check is green — a release that fails CI is worse than a delayed one.
AppVersion lives in cmd/gocron/gocron.go.1.6.7 → 1.7.0). Fix/chore only → bump patch
(1.6.7 → 1.6.8). Matches the project's history (v1.5.9 → v1.6.0 was a minor).AppVersion in cmd/gocron/gocron.go.ToNumberVersion maps the string to an int (1.7.0 → 170). If this release
adds a DB migration, its versionId + upgradeForNNN in
internal/models/migration.go MUST use that same number (e.g. 170), and the
Upgrade chain must include it. Add a migration test.AppVersion changes.Run the /verify command (or the steps in CLAUDE.md → "Pre-commit / release
checks"): gofmt, go vet, golangci-lint, go test -race, and the frontend
build/typecheck/lint. go build/go test alone are NOT sufficient — lint is a
separate gate. Fix everything until all steps are green.
chore(release): bump version to X.Y.Z (short subject;
commitlint rejects > 100 chars).master (fast-forward preferred).git tag -a vX.Y.Z -m "vX.Y.Z" && git push origin vX.Y.Z
(annotated tag). release.yml listens on v* tags to build/publish artifacts.Migrations that rewrite existing rows (e.g. remapping notify_status) can't be
undone — remind the user to back up the database before upgrading, and note the
change in the release notes.
master; use a branch.Co-Authored-By lines to commits.