agentleFS
Sign inStart free
tonmoy007tonmoy007/forge-plugins/skills/forge-release/SKILL.md

forge-release

Skill2 starsChanged 5 months agoMITView on GitHub

Run Stage 12 of the Forge pipeline — release preparation. Use when the

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read pipeline/state.md — confirm Forge project.

    line 19
  2. Distinctive:

    If not: "A passing evaluation (Stage 7) is required before cutting a release."

    line 21
  3. Distinctive:

    Check that no critical or high-severity items from triage remain unresolved.

    line 22
  4. Very specific:

    Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd .

    line 23
  5. Very specific:

    Read agents/release-manager.md to load the Release Manager persona.

    line 27
  6. Distinctive:

    Run git log via Bash to enumerate commits since the last release tag.

    line 29
  7. Very specific:

    Follow the Release Manager workflow: classify changes, determine version bump, write changelog and release notes.

    line 30
  8. Very specific:

    Write pipeline/12-release/CHANGELOG.md and pipeline/12-release/release-notes.md (plus a migration guide when the profile requires it).

    line 31
  9. Very specific:

    Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py advance --to 12 to mark Stage 12 active.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/forge:release — Release

When to Use

  • User says /forge:release
  • User wants to cut a release, bump the version, write a changelog, or prepare release notes
  • Working in a Forge project at Stage 11 or 12

Pre-flight Check

  1. Read pipeline/state.md — confirm Forge project.
  2. Confirm pipeline/07-evaluation/eval-report.md exists and shows overall pass. If not: "A passing evaluation (Stage 7) is required before cutting a release."
  3. Check that no critical or high-severity items from triage remain unresolved.
  4. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 12 to load project-type release criteria. For library projects this surfaces G12-LIB-001 (Keep a Changelog format), G12-LIB-002 (semver enforced — breaking changes → major bump), and G12-LIB-003 (migration guide for breaking changes) — all must be addressed in the release artifacts.

Steps

  1. Read agents/release-manager.md to load the Release Manager persona.
  2. Adopt that persona — you are now the Release Manager.
  3. Run git log via Bash to enumerate commits since the last release tag.
  4. Follow the Release Manager workflow: classify changes, determine version bump, write changelog and release notes. Address every profile additional_criteria from pre-flight as a deliverable.
  5. Write pipeline/12-release/CHANGELOG.md and pipeline/12-release/release-notes.md (plus a migration guide when the profile requires it).
  6. Bump version fields in the project's version files (package.json, pyproject.toml, etc.).
  7. Write pipeline/12-release/post-release-checklist.md.
  8. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py advance --to 12 to mark Stage 12 active.

Verification

After running, confirm:

  • pipeline/12-release/CHANGELOG.md exists with semantic version and categorized changes
  • pipeline/12-release/release-notes.md exists (user-facing language)
  • Version bumped consistently across all version files
  • pipeline/state.md shows current_stage: 12

Next Step

Derive the hint from the canonical stage table — never hardcode it (REQ-NEXTHINT-001, single source of truth). Run the helper and present its output to the user verbatim:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py next-hint --stage 12

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free