release skills

Productivity Community

Skill notes

User Input Tools

When this skill prompts the user, follow this tool-selection rule (priority order): Prefer built-in user-input tools exposed by the current agent runtime — e.g., AskUserQuestion, request_user_input, clarify, ask_user, or any equivalent. Fallback: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each question. Batching: if the tool supports multiple questions per call, combine all applicable questions into a single call; if only single-question, ask them one at a time in priority order.

Quick Start

Just run /release-skills - auto-detects your project configuration.

Supported Projects

Project Type · Version File · Auto-Detected Node.js · package.json · ✓ Python · pyproject.toml · ✓ Rust · Cargo.toml · ✓ Claude Plugin · marketplace.json · ✓

Options

Flag · Description --dry-run · Preview changes without executing --major · Force major version bump --minor · Force minor version bump --patch · Force patch version bump

Step 1: Detect Project Configuration

Check for .releaserc.yml (optional config override) If present, inspect whether it defines release hooks Auto-detect version file by scanning (priority order): package.json (Node.js) pyproject.toml (Python)

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
@JimLiu · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

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

01
Step 1: Detect Project Configuration

Check for `.releaserc.yml` (optional config override) If present, inspect whether it defines release hooks Auto-detect version file by scanning (priority order): `package.json` (Node.js) `pyproject.toml` (Python)

02
Step 2: Analyze Changes Since Last Tag

Categorize by conventional commit types: Type · Description feat · New features fix · Bug fixes docs · Documentation

03
Step 3: Determine Version Bump

Rules (in priority order): User flag `--major/--minor/--patch` → Use specified BREAKING CHANGE detected → Major bump (1.x.x → 2.0.0) `feat:` commits present → Minor bump (1.2.x → 1.3.0) Otherwise → Patch bump (1.2.3 → 1.2.4)

04
Step 4: Generate Multi-language Changelogs

For each detected changelog file: Identify language from filename suffix Detect third-party contributors: Check merge commits: `git log ${LAST_TAG}..HEAD --merges --pretty=format:"%H %s"` For each merged PR, identify the PR author via `gh pr view <number> --json author --jq '.author.login'`

05
Step 5: Group Changes by Skill/Module

Analyze commits since last tag and group by affected skill/module: Identify changed files per commit Group by skill/module: `skills/<skill-name>/*` → Group under that skill Root files (CLAUDE.md, etc.) → Group as "project"

06
Step 6: Commit Each Skill/Module Separately

For each skill/module group (in order of changes): Check README updates needed: Scan `README*.md` for mentions of this skill/module Verify options/flags documented correctly Update usage examples if syntax changed

07
Step 7: Generate Changelog and Update Version

Generate multi-language changelogs (as described in Step 4) Update version file: Read version file (JSON/TOML/text) Update version number Write back (preserve formatting)

08
Step 8: User Confirmation

Before creating the release commit, ask user to confirm: Use AskUserQuestion with three questions: Version bump (single select): Show recommended version based on Step 3 analysis Options: recommended (with label), other semver options

09
Step 9: Create Release Commit and Annotated Tag

After user confirmation: Stage version and changelog files: Create release commit: Create annotated tag: If `.releaserc.yml` sets `tag.sign: true`, use `git tag -s` with the same notes file.

10
Step 10: Publish Release Artifacts and GitHub Release

Project artifact publishing and GitHub Releases are separate outputs: Project artifacts: If `release.hooks.publish_artifact` exists, run it once per prepared target Pass the same `{release_notes_file}` used for the tag and GitHub Release In dry-run mode, pass `{dry_run}=true` and report what would be published

Discussion

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