coferlandia-release-maintainer

Coordinates skill versions, changelogs, release notes, and plugin packaging through one deterministic release gate.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/coferlandia/coferlandia-skills --skill coferlandia-release-maintainer-coferlandia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coferlandia-release-maintainer
Source: https://github.com/coferlandia/coferlandia-skills/tree/main/.agents/skills/coferlandia-release-maintainer
Command: npx skills add https://github.com/coferlandia/coferlandia-skills --skill coferlandia-release-maintainer-coferlandia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Releasing changes in the coferlandia-skills repository requires keeping per-skill versions, changelogs, the plugin manifest version, release notes, and the README summary perfectly synchronized, and doing this manually leads to drift, stale documentation, and inconsistent packages. ## Core Features & Use Cases - Diff-aware inspection: Classifies the complete delivery diff against an integration base into skill, plugin, protocol, documentation, and local-only changes. - Deterministic preparation: Applies a release plan to bump skill versions, update changelogs, regenerate RELEASE-NOTES.md sections, and refresh the managed README release block. - Release-ready gate and packaging: Validates version consistency across all surfaces and builds a verified plugin archive with SHA-256 digest, excluding repository-local files. - Use Case: Before merging a branch that changed two public skills, run the inspect, prepare, check --release-ready, and package --verify commands to produce a consistent release and an exact suggested commit message. ## Quick Start Ask the agent to run the coferlandia release-maintainer inspect and check commands against your integration base, then prepare and verify the plugin package before the final commit.

Frequently Asked Questions about coferlandia-release-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a release for the coferlandia-skills repository?▼

Create a release plan JSON with the release version, date, impact, and per-skill version changes, then run the CLI prepare command. It updates SKILL.md versions, changelogs, plugin.json, RELEASE-NOTES.md, and the README release block deterministically.

How do I validate release readiness before merging a branch?▼

Run the check command with --base and --release-ready flags alongside validate_skill.py and bump_version.py --check and --audit. The gate fails if any changed skill lacks a version bump, changelog entry, or release-note row, or if versions drift across surfaces.

When should this release skill activate?▼

It activates only near final delivery: the final commit, PR readiness, integration, version bumps, or packaging. It should not run for intermediate checkpoint commits, RED test additions, or repositories other than coferlandia-skills.

Does the release-maintainer commit, tag, or publish releases?▼

No. The skill never commits, pushes, merges, tags, or publishes a GitHub Release. It only prepares artifacts, validates the gate, and builds the verified package; the active Git authority performs those actions afterward.

What does the plugin package include and exclude?▼

The package includes .claude-plugin, skills, prompts, _protocol, README, AGENTS, SKILLS-GUIDE, RELEASE-NOTES, and LICENSE. It excludes .agents, .agent, Git state, caches, and secrets, and verification reopens the archive to confirm contents and record the SHA-256 digest.