菜单
Pre-release checklist for Forge — verify, version bump, changelog, docs, docker build, smoke test. Run before tagging v*.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deep review — random exploration + cross-agent review, alternating. Finds integration bugs that self-review misses. Run every 30–60 min during active implementation.
Overview of Forge's Agentic Coding Flywheel methodology. Use to route between plan, bead, and code space. See FLYWHEEL.md at the repo root.
End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.
Start a new Flywheel planning round. Produce initial markdown plan, route to competing frontier models, synthesize hybrid, refine 4–5×. Use before any coding begins on a new feature.
Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Every bead must be executable without reopening the plan. Use after the plan has converged.
Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.
| name | release-check |
| description | Pre-release checklist for Forge — verify, version bump, changelog, docs, docker build, smoke test. Run before tagging v*. |
A bad release is worse than a late release. Do each step manually.
git status # must be clean
git fetch origin
git log --oneline origin/master..HEAD # what's going out
package.json version bumped per semver.CHANGELOG.md has a section for this version (Added / Changed /
Fixed / Security), referencing issues/PRs.All 249+ tests pass; format, lint, typecheck, build all clean.
docs/ARCHITECTURE.md reflects hot-path changes.docs/SETUP.md / docs/INSTALL.md reflect new env vars or deps.bash scripts/metrics.sh.docker build -f docker/Dockerfile -t forge:dev .
docker run --rm forge:dev doctor --no-banner
npm run build
./bin/forge.js doctor
./bin/forge.js --version
Only after every step above passes. The tag triggers a 6-stage release workflow — do not push one you haven't verified.
git tag v<x.y.z>
git push origin v<x.y.z>