release and publish

AI Community

Skill notes

Preconditions

This skill runs after git wrapup. By the time it's invoked: package.json version is bumped server.json version is bumped (top-level + each package entry) CHANGELOG.md has a new entry for this version with a concrete date (never [Unreleased]) README badges and version-bearing files are in sync

Failure Protocol

Stop on the first non-zero exit. No retries, no remediation from inside the skill. Report to the user: Which step failed The exact error output Which destinations already received the release (npm published? tag pushed?) so they know the partial state The user fixes locally and re-invokes, or runs the remaining steps manually. Publishes hard-fail with "version already exists" if replayed — that's the signal the step already succeeded.

1. Sanity-check wrapup outputs

Read package.json → capture version. Read server.json → verify top-level version matches and every packages[].version matches. Then verify git state: If working tree is dirty, HEAD isn't on v<version>, or server.json versions drift from package.json, halt.

2. Run the verification gate

All three must succeed: Any non-zero exit → halt with the failing command's output. devcheck runs lint + format + typecheck + bun audit. rebuild is a clean + bun build to catch build-time regressions devcheck alone can miss.

3. Push to origin

If the remote rejects either push, halt. On a fresh branch, git push may need -u origin <branch> — read the error and re-run if that's the only gap.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · GitHub
Operating systems
macOS
Runtime requirements
Bun
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview release-and-publish.preview
# 1. Sanity-check wrapup outputs

git status --porcelain                         # must be empty — clean working tree
git describe --exact-match --tags HEAD 2>&1    # must equal v<version>
git rev-parse --abbrev-ref HEAD                # note the branch name

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.