GitHub Release自动化发布工具 - 安全检查与版本发布工作流

github-release by jezweb/claude-skills

403 周安装量

650 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/jezweb/claude-skills --skill github-release

开发自动化安全

🇨🇳中文介绍

GitHub 发布

清理项目并发布到 GitHub。两阶段工作流程：先进行安全检查，然后打标签并发布。

前提条件

已安装并认证 gh CLI (gh auth status)
已安装 gitleaks 用于扫描密钥 (brew install gitleaks 或从 GitHub 下载)
已配置远程仓库的 Git 仓库

工作流程

阶段 1：清理

在公开发布前运行这些检查。遇到阻塞项则停止。

1. 扫描密钥（阻塞项）

gitleaks detect --no-git --source=. --verbose

如果发现密钥：停止。移除密钥，将其移至环境变量。使用 git log -S "secret_value" 检查 git 历史记录——如果存在于历史记录中，请使用 BFG Repo-Cleaner。

如果未安装 gitleaks，请手动检查：

# 检查 .env 文件
find . -name ".env*" -not -path "*/node_modules/*"

# 检查配置文件中的硬编码密钥
grep -ri "api_key\|token\|secret\|password" wrangler.toml wrangler.jsonc .dev.vars 2>/dev/null

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

FlyClaw：零登录航班聚合查询工具，Python实现多源航班信息与价格搜索

4,000,000 周安装

find-skills 技能搜索工具 - Vercel Labs 开源智能体技能包管理器

762,600 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

258,600 周安装

Vercel Web界面规范检查工具 - 自动检测代码是否符合Web设计指南

208,300 周安装

2. 移除个人工作文件

检查并移除不应发布的会话/规划文件：

SESSION.md — 会话状态
planning/, screenshots/ — 工作目录
test-*.ts, test-*.js — 本地测试文件

删除它们或将其添加到 .gitignore。

ls LICENSE LICENSE.md LICENSE.txt 2>/dev/null

如果缺失：创建一个。检查仓库可见性 (gh repo view --json visibility -q '.visibility')。公共仓库使用 MIT 许可证。对于私有仓库，请考虑使用专有许可证。

检查 README 是否存在并具有基本部分：

grep -i "## Install\|## Usage\|## License" README.md

如果缺少部分，请在发布前添加。

5. 检查 .gitignore

验证是否存在必要的模式：

grep -E "node_modules|\.env|dist/|\.dev\.vars" .gitignore

6. 构建测试（非阻塞项）

npm run build 2>&1

7. 依赖项审计（非阻塞项）

npm audit --audit-level=high

8. 创建清理提交

如果在清理过程中进行了任何更改：

git add -A
git commit -m "chore: prepare for release"

检查 package.json 中的当前版本，或询问用户。确保版本以 v 前缀开头。

2. 检查标签是否不存在

git tag -l "v[version]"

如果存在，询问用户是删除并重新创建还是使用其他版本。

3. 显示将要发布的内容

LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
  git log --oneline --no-merges HEAD | head -20
else
  git log --oneline --no-merges ${LAST_TAG}..HEAD
fi

4. 创建标签并推送

git tag -a v[version] -m "Release v[version]"
git push origin $(git branch --show-current)
git push origin --tags

5. 创建 GitHub 发布

gh release create v[version] \
  --title "Release v[version]" \
  --notes "[auto-generated from commits]"

对于预发布版本，添加 --prerelease。对于草稿，添加 --draft。

发布 URL
后续步骤（如果适用，发布到 npm，发布公告）

何时	阅读
详细安全检查	references/safety-checklist.md
发布机制	references/release-workflow.md

🇺🇸English

GitHub Release

Sanitize and release projects to GitHub. Two-phase workflow: safety checks first, then tag and publish.

Prerequisites

gh CLI installed and authenticated (gh auth status)
gitleaks installed for secrets scanning (brew install gitleaks or download from GitHub)
Git repository with a remote configured

Workflow

Phase 1: Sanitize

Run these checks before any public release. Stop on blockers.

1. Scan for Secrets (BLOCKER)

gitleaks detect --no-git --source=. --verbose

If secrets found: STOP. Remove secrets, move to environment variables. Check git history with git log -S "secret_value" — if in history, use BFG Repo-Cleaner.

If gitleaks not installed, do manual checks:

# Check for .env files
find . -name ".env*" -not -path "*/node_modules/*"

# Check config files for hardcoded secrets
grep -ri "api_key\|token\|secret\|password" wrangler.toml wrangler.jsonc .dev.vars 2>/dev/null

2. Remove Personal Artifacts

Check for and remove session/planning files that shouldn't be published:

SESSION.md — session state
planning/, screenshots/ — working directories
test-*.ts, test-*.js — local test files

Either delete them or add to .gitignore.

3. Validate LICENSE

ls LICENSE LICENSE.md LICENSE.txt 2>/dev/null

If missing: create one. Check the repo visibility (gh repo view --json visibility -q '.visibility'). Use MIT for public repos. For private repos, consider a proprietary license instead.

4. Validate README

Check README exists and has basic sections:

grep -i "## Install\|## Usage\|## License" README.md

If missing sections, add them before release.

5. Check .gitignore

Verify essential patterns are present:

grep -E "node_modules|\.env|dist/|\.dev\.vars" .gitignore

6. Build Test (non-blocking)

npm run build 2>&1

7. Dependency Audit (non-blocking)

npm audit --audit-level=high

8. Create Sanitization Commit

If any changes were made during sanitization:

git add -A
git commit -m "chore: prepare for release"

Phase 2: Release

1. Determine Version

Check package.json for current version, or ask the user. Ensure version starts with v prefix.

2. Check Tag Doesn't Exist

git tag -l "v[version]"

If it exists, ask user whether to delete and recreate or use a different version.

3. Show What's Being Released

LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
  git log --oneline --no-merges HEAD | head -20
else
  git log --oneline --no-merges ${LAST_TAG}..HEAD
fi

4. Create Tag and Push

git tag -a v[version] -m "Release v[version]"
git push origin $(git branch --show-current)
git push origin --tags

5. Create GitHub Release

gh release create v[version] \
  --title "Release v[version]" \
  --notes "[auto-generated from commits]"

For pre-releases add --prerelease. For drafts add --draft.

6. Report

Show the user:

Release URL
Next steps (npm publish if applicable, announcements)

Reference Files

When	Read
Detailed safety checks	references/safety-checklist.md
Release mechanics	references/release-workflow.md

Weekly Installs

393

Repository

jezweb/claude-skills

GitHub Stars

643

First Seen

Feb 18, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode353

codex348

github-copilot348

gemini-cli347

cursor341

kimi-cli337

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

138,300 周安装