release
- Repo stars 6,503
- License Apache-2.0
- Author updated Live
- Author repo plano
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @katanemo · Apache-2.0
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: release
description: Bump the Plano version across all required files. Use when preparing a release. Prepare a releas…
category: other
runtime: no special runtime
---
# release output preview
## PART A: Task fit
- Use case: Bump the Plano version across all required files. Use when preparing a release. Prepare a release version bump. The user may provide the new version number as $ARGUMENTS (e.g., /release 0.4.12), or a bump type (major, minor, patch). runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Bump the Plano version across all required files. Use when preparing a release. Prepare a release version bump. The user may provide the new version number as $ARGUMENTS (e.g., /release 0.4.12), or a bump type (major, minor, patch). runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/release`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: release
description: Bump the Plano version across all required files. Use when preparing a release. Prepare a releas…
category: other
source: katanemo/plano
---
# release
## When to use
- Bump the Plano version across all required files. Use when preparing a release. Prepare a release version bump. The us…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "release" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Prepare a release version bump. The user may provide the new version number as $ARGUMENTS (e.g., /release 0.4.12), or a bump type (major, minor, patch).
If no argument is provided, read the current version from cli/planoai/__init__.py, auto-increment the patch version (e.g., 0.4.11 → 0.4.12), and confirm with the user before proceeding.
Update the version string in ALL of these files:
.github/workflows/ci.ymlcli/planoai/__init__.pycli/planoai/consts.pycli/pyproject.tomlbuild_filter_image.shconfig/validate_plano_config.shdocs/source/conf.pydocs/source/get_started/quickstart.rstdocs/source/resources/deployment.rstapps/www/src/components/Hero.tsxdemos/llm_routing/preference_based_routing/README.md
Do NOT change version strings in *.lock files or Cargo.lock.
After updating all version strings, run cd cli && uv lock to update the lock file with the new version.
After making changes, show a summary of all files modified and the old → new version.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review