メニュー
Reproduce the complete gocron CI pipeline locally and report every result. Use before commits, pull requests, merges, tags, or releases; when asked to verify, check, lint, test, build, or determine whether the repository is ready to ship.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/gocronx-team/gocron --skill verifyコマンドは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 | verify |
| description | Reproduce the complete gocron CI pipeline locally and report every result. Use before commits, pull requests, merges, tags, or releases; when asked to verify, check, lint, test, build, or determine whether the repository is ready to ship. |
Run from the repository root. Treat .github/workflows/ci.yml as the source of
truth if it differs from this skill.
git status --short before running checks.Do not stop after the first failure. Record the exit status and useful output for each independent check.
gofmt -l .. Any listed Go file is a failure; do not run gofmt -w
unless fixes were requested.go vet ./....golangci-lint run ./.... CI uses v2.12.2; report a missing or
incompatible local version instead of silently substituting another version.go test -race -coverprofile=coverage.out ./....web/gocronx-admin, run these as separate checks so one failure does not
hide the others:
pnpm build-onlypnpm exec vue-tsc --noEmitpnpm lintdocker build -f Dockerfile.gocron -t gocron:ci ..If dependencies or tools are missing, clearly distinguish an environment failure from a code failure. Installing tools or packages may require network access; obtain any required approval and use the versions pinned by the repo or CI. Do not claim the check passed when it was skipped.
End with a compact table containing each check, pass/fail/skipped status, and
the actionable error. Include exact file:line locations where available.
Mention whether coverage.out or generated frontend files changed the working
tree.
Say the repository is ready to commit, merge, or release only when every required check passes, including the Docker build.