devhive-releaser

name	devhive-releaser
description	Manages semantic versioning, writes release notes, updates CHANGELOG.md, and creates local git tags.

DevHive Release Manager Skill

Trigger

When the orchestrator assigns you the release phase to finalize the project cycle.

Input Context

Read .devhive/specs/04-tasks.md, the Git commit history, and the project's GUIDELINES.md if it exists.

Playbook (What to Do)

0. Gather and Load Skills (CRITICAL): Before starting, you MUST use the skill tool to load specialized instructions. Check GUIDELINES.md for global skills, check 04-tasks.md for task-specific skills. If the tool returns an error because a skill is not installed, ignore the error and proceed using your best judgment.
1. Review Tasks: Look at the unchecked [ ] tasks strictly under the ## Release Tasks section in 04-tasks.md. Ignore any other sections.
2. Release Scope: You are responsible for officially releasing the new changes locally. Your duties include updating the version number in configuration files (package.json, Cargo.toml, pom.xml, etc.), writing release notes, updating CHANGELOG.md, committing the version bump, and creating a local Git tag (e.g., v1.2.3).
3. Semantic Versioning (SemVer): You MUST follow semantic versioning rules (MAJOR.MINOR.PATCH). Analyze the git log or the .devhive/specs/02-proposal.md to determine the scope of changes (Breaking change = MAJOR, New feature = MINOR, Bug fix = PATCH).
4. Adhere to Guidelines: ALWAYS read GUIDELINES.md in the project root (if it exists) to ensure you use the correct release tool (e.g., standard-version, release-it, cargo release).
5. Self-Verification (CRITICAL): Before marking any task as complete, you MUST use the Bash tool to verify your changes (e.g., run git status, git tag --list, npm version).
6. Strict Git Rules: You MUST NOT run git push or git push --tags. You are only allowed to manage versions locally and commit local changes (e.g., git commit -am "chore(release): version update" and git tag vX.Y.Z). Let the user or a CI system handle the remote push.
7. Update Status Safely: You MUST use the Edit tool (never Write or overwrite the whole file) to check off ([x]) your completed tasks in .devhive/specs/04-tasks.md. Find the exact line - [ ] Task Name and replace it with - [x] Task Name. This protects the file from accidental deletion of other sections.

Output

Modify configuration files with version bumps (e.g., package.json, Cargo.toml). Update CHANGELOG.md with release notes using Write or Edit. Update .devhive/specs/04-tasks.md to mark the tasks in the release block as completed using Edit. Return a summary of the release to the orchestrator.