القائمة
Automate semver releases — bump version, generate changelog, tag, and publish GitHub Release.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/qhkm/zeptoclaw-skills --skill git-releaseيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Give your agent a standalone on-chain wallet for gasless trades, funding, and autonomous x402 M2M payments.
Deploy ERC20 tokens on Base, Ethereum, Arbitrum, and other EVM chains using the Clanker SDK. Use when the user wants to deploy a new token, create a memecoin, set up token vesting, configure airdrops, manage token rewards, claim LP fees, or update token metadata. Supports V4 deployment with vaults, airdrops, dev buys, custom market caps, vanity addresses, and multi-chain deployment.
AI-powered crypto trading agent and LLM gateway via natural language. Use when the user wants to trade crypto, check portfolio balances, view token prices, transfer crypto, manage NFTs, use leverage, bet on Polymarket, deploy tokens, set up automated trading, sign and submit raw transactions, or access LLM models through the Bankr LLM gateway funded by your Bankr wallet. Supports Base, Ethereum, Polygon, Solana, and Unichain.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | git-release |
| version | 1.0.0 |
| description | Automate semver releases — bump version, generate changelog, tag, and publish GitHub Release. |
| author | ZeptoClaw |
| license | MIT |
| tags | ["git","release","devops","changelog","semver"] |
| env_needed | [{"name":"GITHUB_TOKEN","description":"Personal access token with repo scope (for creating GitHub Releases)","required":true},{"name":"GH_REPO","description":"Repository in owner/repo format (e.g. myorg/myapp)","required":true}] |
| metadata | {"zeptoclaw":{"emoji":"🚀","requires":{"anyBins":["git","gh","jq"]}}} |
Automate the full release workflow: semver bump → changelog → git tag → GitHub Release.
export GITHUB_TOKEN="ghp_xxx..."
export GH_REPO="myorg/myapp"
Or if already logged in with gh auth login, skip GITHUB_TOKEN — the gh CLI uses its own token.
# Show last tag
git describe --tags --abbrev=0
# Commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline
# Count breaking / feat / fix
git log $(git describe --tags --abbrev=0)..HEAD --oneline | grep -c "^.*feat"
git log $(git describe --tags --abbrev=0)..HEAD --oneline | grep -c "^.*fix"
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
MAJOR=$(echo $LAST_TAG | sed 's/v//' | cut -d. -f1)
MINOR=$(echo $LAST_TAG | sed 's/v//' | cut -d. -f2)
PATCH=$(echo $LAST_TAG | sed 's/v//' | cut -d. -f3)
# Bump patch (bug fixes only)
NEXT="v${MAJOR}.${MINOR}.$((PATCH + 1))"
# Bump minor (new features, no breaking changes)
NEXT="v${MAJOR}.$((MINOR + 1)).0"
# Bump major (breaking changes)
NEXT="v).0.0"
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
RANGE="${LAST_TAG:+${LAST_TAG}..}HEAD"
# Categorized changelog
BREAKING=$(git log $RANGE --oneline | grep -i "BREAKING\|!:" || true)
FEATURES=$(git log $RANGE --oneline | grep -i "^[a-f0-9]* feat" || true)
FIXES=$(git log $RANGE --oneline | grep -i "^[a-f0-9]* fix" || true)
OTHERS=$(git log $RANGE --oneline | grep -iv "^[a-f0-9]* \(feat\|fix\|chore\|docs\)" || true)
cat << EOF
## What's Changed
${BREAKING:+### Breaking Changes
$BREAKING
}${FEATURES:+### Features
$FEATURES
}${FIXES:+### Bug Fixes
$FIXES
}${OTHERS:+### Other Changes
$OTHERS
}
**Full Changelog**: https://github.com/$GH_REPO/compare/${LAST_TAG}...${NEXT}
EOF
NEXT="v1.2.0" # set your version
# Create annotated tag
git tag -a "$NEXT" -m "Release $NEXT"
# Push tag
git push origin "$NEXT"
echo "Tag $NEXT pushed"
# Generate notes and create release
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null | head -1)
NOTES=$(git log ${LAST_TAG:+${LAST_TAG}..}HEAD --oneline \
| sed 's/^[a-f0-9]* /- /' \
| head -30)
gh release create "$NEXT" \
--title "Release $NEXT" \
--notes "## What's Changed
$NOTES
**Full Changelog**: https://github.com/$GH_REPO/compare/${LAST_TAG}...${NEXT}" \
--verify-tag
# Build first (adjust for your stack)
# cargo build --release
# npm run build
# Upload artifacts
gh release upload "$NEXT" \
./target/release/myapp \
./target/release/myapp.tar.gz \
--clobber
# Set version
NEXT="v1.2.0"
LAST=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
# Tag
git tag -a "$NEXT" -m "Release $NEXT" && git push origin "$NEXT"
# Release
gh release create "$NEXT" \
--generate-notes \
--title "Release $NEXT"
echo "Released: https://github.com/$GH_REPO/releases/tag/$NEXT"
--generate-notes with gh release create — GitHub auto-generates changelog from PRsCargo.toml version before tagging: sed -i "s/^version = .*/version = \"1.2.0\"/" Cargo.tomlnpm version patch/minor/major auto-bumps package.json and creates a commit + tagv prefix (v1.2.0) — most tools expect it--draft, review, then gh release edit $NEXT --draft=false