菜单
Prepare an ai-moderation-challenge release by analyzing commits, choosing a version bump, verifying the package, running release-it, and checking publish workflow expectations. Use when the user says "release", "new version", "cut a release", "prepare release", or provides a version number to ship.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Formats GitHub commit messages following Conventional Commits style with a title and optional description. Use when proposing or implementing code changes, writing commit messages, or when the user asks for commit message suggestions.
Commit current work by reviewing diffs, splitting into logical commits, and writing standardized messages. Use when the user says "commit", "commit this", "commit current work", or asks to create a git commit.
Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. Use when looking up documentation for a programming library, verifying APIs, or obtaining current library examples.
Systematic evidence-based debugging using runtime logs or focused reproductions. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Scan recent changes for AI-generated code slop and remove it. Use when the user says "deslop", "remove slop", "clean up AI code", or asks to remove AI-generated artifacts from the codebase.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities.
| name | release |
| description | Prepare an ai-moderation-challenge release by analyzing commits, choosing a version bump, verifying the package, running release-it, and checking publish workflow expectations. Use when the user says "release", "new version", "cut a release", "prepare release", or provides a version number to ship. |
The user should provide a bump (patch, minor, major) or explicit x.y.z. If omitted, ask which bump level they want.
Track progress with this checklist:
Release Progress:
- [ ] Step 1: Inspect current version and latest tag
- [ ] Step 2: Analyze commits since latest tag
- [ ] Step 3: Verify package
- [ ] Step 4: Run release-it
- [ ] Step 5: Inspect generated changelog, version, tag, and release notes
- [ ] Step 6: Push only if the user asked
node -p "require('./package.json').version"
git tag --sort=-creatordate | head -1
git log --oneline <tag>..HEAD
If there are no new commits, stop.
corepack yarn install --immutable
corepack yarn build
corepack yarn type-check
corepack yarn test
corepack yarn format:check
Remove generated dist/ after local verification unless the release command needs it.
Use the repo script and pass the intended increment or explicit version:
corepack yarn release --ci --increment patch
or:
corepack yarn release --ci --increment 0.1.2
The release-it config updates CHANGELOG.md, bumps package.json, commits, tags, and creates a GitHub release. Npm publishing is handled later by .github/workflows/publish.yml when the version change lands on master.
git status --short
git log --oneline -3
git tag --sort=-creatordate | head -3
Confirm CHANGELOG.md and package.json reflect the intended release.
Do not push commits or tags unless the user explicitly asks.
If the user says "dry run" or "preview", do Steps 1-3 and report the planned bump and release summary without running release-it.