메뉴
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명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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.