Individual skill
release
Use when the user asks to release, version, tag, or publish.
plugins/ouonet/praxis/skills/release/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 960 bytes
Read excerpt
# Release
Use only when the user asks to release.
If `topology=multi-module` (triage announcement or coordinator spec/plan declaration), read `../references/multi-module.md`. Release only the exact coordinator revision set that passed integration. Determine version and dependency order per repository, and keep the existing approval gates for each repository's commit, tag, push, or publish. A completed change set does not itself authorize a release.
1. Confirm version/bump.
2. Start from green tests and clean tree.
3. Update version files.
4. Move CHANGELOG `Unreleased` to `version - date`; create new `Unreleased`.
`<gate>` Steps 5-7 touch shared or irreversible state. Get explicit user approval before **each** step — never chain them on one confirmation. `</gate>`
5. Commit release edits.
6. Create annotated tag.