菜单
End-to-end tsforge release — validate, commit pending work, bump version, signed tag, push, watch npm publish. Use when the user asks to release, publish, ship, tag, or cut a version. Does not require a clean git tree. Manual-only; do not auto-run during unrelated tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
How to write and maintain tsforge agent skills — when to use a skill vs a rule vs a recipe vs docs, description routing, progressive disclosure, and the ship checklist. Use when creating, editing, or reviewing SKILL.md files under .claude/skills/, or when asked "should this be a skill?".
Adversarially review one tsforge harness subsystem (or all) against its invariants. Use when asked to "review the harness", "audit a subsystem", "check the gate/tools/loop/process layer", or before a release. Reads source + tests, checks each invariant, repros suspected breaks, and returns a structured findings list.
| name | tsforge-release |
| description | End-to-end tsforge release — validate, commit pending work, bump version, signed tag, push, watch npm publish. Use when the user asks to release, publish, ship, tag, or cut a version. Does not require a clean git tree. Manual-only; do not auto-run during unrelated tasks. |
| disable-model-invocation | true |
One command from dirty main to npm + GitHub Release. Pushing v*.*.* triggers .github/workflows/release.yml.
The script commits everything for you. Uncommitted work is included in the release commit. You do not need a clean tree first.
./scripts/release.sh --tag-only --yes # first publish at current version (e.g. 0.1.0)
./scripts/release.sh patch --yes # later: 0.1.0 → 0.1.1
./scripts/release.sh minor --yes
./scripts/release.sh major --yes
./scripts/release.sh patch --dry-run # preview only
main branchgit fetch origin mainbun run validate (unless --skip-validate)packages/core, root, and apps/docs package.json (unless --tag-only)git add -A + signed commit: chore: release X.Y.Z (pending work + version bump together)origin/main if behindvX.Y.Zmain + tagrelease.yml via gh run watchFlags: --dry-run, --no-push, --yes, --tag-only, --skip-validate.
| Requirement | Check |
|---|---|
gh authenticated | gh auth status |
| Signed commits/tags | git commit -S and git tag -s must work |
NPM_TOKEN on GitHub | gh secret list | grep NPM_TOKEN |
On main | not a feature branch |
When the user asks to release, run the script. Do not ask them to commit first.
git branch --show-current (must be main; checkout main if they explicitly want to release from current work)jq -r .version packages/core/package.json--tag-only. Otherwise patch / minor / major unless they specify../scripts/release.sh <bump> --yesgh run view --log-failed on the release workflowbun install -g @agjs/tsforge@VERSIONDo not manually npm publish unless the user explicitly asks to bypass CI.
packages/core/package.json without the v prefixmain)--tag-only for first publish when version is already set (e.g. 0.1.0)| Failure | Fix |
|---|---|
must be on main | git checkout main |
main diverged from origin/main | resolve rebase conflict, re-run |
tag vX.Y.Z already exists | next semver or delete abandoned tag |
| npm publish 401/403 | Regenerate NPM_TOKEN: granular token with Read and write, All packages, Bypass 2FA for automation (or classic Automation token). Verify npm email. gh secret set NPM_TOKEN |
| npm publish 403 name conflict | Unscoped tsforge conflicts with ts-forge on npm — publish as @agjs/tsforge |
| unsigned commit rejected | enable GPG/SSH signing |