القائمة
Create a new release with a semver tag and GitHub release. Triggers: 'release', 'cut a release', 'tag a new version', 'create release'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Core development loop for making code changes. Use when implementing features, fixing bugs, or refactoring. Triggers: 'implement', 'make a change', 'add feature', 'fix bug'.
Full lifecycle from GitHub issue to merged PR. Reads the issue, creates a branch, implements the fix/feature, verifies, and opens a PR. Triggers: 'pickup issue #N', 'work on issue', 'grab an issue'.
Ship changes via pull request. Runs verification, pushes, and creates a PR targeting main. Triggers: 'create PR', 'open PR', 'ship it', 'submit for review'.
Local CI mirror. Run all checks that GitHub Actions runs before pushing. Use before creating PRs or to debug CI failures. Triggers: 'verify', 'check', 'run CI locally', 'pre-push check'.
| name | release |
| description | Create a new release with a semver tag and GitHub release. Triggers: 'release', 'cut a release', 'tag a new version', 'create release'. |
Tag and publish a new release. This repo uses semantic versioning (v0.x.y).
Check the latest tag:
git tag --sort=-v:refname | head -5
Follow semver:
git checkout main
git pull origin main
golangci-lint run ./... && make citest
All checks must pass before tagging.
git tag v<VERSION>
git push origin v<VERSION>
gh release create v<VERSION> --title "v<VERSION>" --generate-notes
The --generate-notes flag auto-generates release notes from merged PRs since the last tag.
gh release view v<VERSION>
Confirm the release appears on GitHub with correct notes.
main branch only-SNAPSHOT.N suffix (e.g., v0.12.0-SNAPSHOT.0)proxy.golang.org) will index the new version automatically after taggingcommon.config.mk and is independent of SDK releasesmaingh release list