promote

Productivity Community

Skill notes

Step 0: Pre-flight checks

Check for untracked .env files that could be accidentally staged: If any .env files would be staged:

Step 1: Commit any uncommitted changes

If the git status above shows uncommitted or untracked changes: Review the diff: git diff and git diff --cached Stage changes selectively — prefer tracked files: git add -u, then review and add any intentional new files individually. Avoid git add -A unless the user explicitly confirms. Draft a conventional commit message from the changes — lead with a type prefix

Step 2: Push

Push the current branch to remote:

Step 3: Merge to main (feature branch only)

Skip this step if already on main (or the repo's default branch). If on a feature branch: Scan commits since the last tag for issue references: Look for Closes #N, Fixes #N, Resolves #N (case-insensitive). Collect all issue numbers found. If none are found:

Step 4: Confirm next version

The next version is pre-calculated in the context block above using these semver rules: Commit subject with !: (e.g. feat!:, fix!:) → major bump Commit subject beginning with feat → minor bump All other commits → patch bump Confirm the calculated version is correct given the commit list. If no previous tag exists, use

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Productivity
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
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

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

01
Step 0: Pre-flight checks

Check for untracked `.env` files that could be accidentally staged: If any `.env` files would be staged:

02
Step 1: Commit any uncommitted changes

If the git status above shows uncommitted or untracked changes: Review the diff: `git diff` and `git diff --cached` Stage changes selectively — prefer tracked files: `git add -u`, then review and add any intentional new files individually. Avoid `git add -A` unless the user explicitly confirms. Draft a conventional commit message from the changes — lead with a type prefix

03
Step 2: Push

Push the current branch to remote:

04
Step 3: Merge to main (feature branch only)

Skip this step if already on `main` (or the repo's default branch). If on a feature branch: Scan commits since the last tag for issue references: Look for `Closes #N`, `Fixes #N`, `Resolves #N` (case-insensitive). Collect all issue numbers found. If none are found:

05
Step 4: Confirm next version

The next version is pre-calculated in the context block above using these semver rules: Commit subject with `!:` (e.g. `feat!:`, `fix!:`) → major bump Commit subject beginning with `feat` → minor bump All other commits → patch bump Confirm the calculated version is correct given the commit list. If no previous tag exists, use

06
Step 5: Sync plugin manifest (if present)

If `.claude-plugin/plugin.json` exists, update its `version` field to `<next-version>` (no `v` prefix — plugin manifests use bare semver like `1.2.3`): Then commit and push: Skip this step entirely if `.claude-plugin/plugin.json` does not exist.

07
Step 6: Tag and release

Step 6: Tag and release

08
Step 7: Close resolved issues (main branch only)

Skip this step if a PR was created in Step 3 — GitHub will close the issues automatically when the PR merges via the `Closes #N` keywords in the PR body. If the promotion was directly on `main` (no PR), close any identified issues now:

09
Step 8: Clean up merged feature branch

If a feature branch was merged in Step 3, delete it locally and remotely:

10
Step 9: Confirm clean state

Report the GitHub release URL from `gh release view v<next-version> --json url --jq '.url'`. Source: ali5ter/claude-workflow-skills — distributed by TomeVault.

Discussion

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