Universal Project Release Workflow
JimLiu/baoyu-skills
Detects a project's version file and changelog format, then runs a release: bumping the version, writing release notes and creating GitHub releases, including backfill.
Unified release coherence workflow for any component (CLI, GHA, or SDK).
Install Release Coherence
$ npx skills add macalbert/envilder --skill release-coherence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install macalbert/envilder release-coherence --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/release-coherence .claude/skills/release-coherence && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-coherence" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/release-coherence into .claude/skills/release-coherence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-coherence", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/macalbert/envilder/tree/main/.github/skills/release-coherenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add macalbert/envilder --skill release-coherence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install macalbert/envilder release-coherence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/release-coherence .agents/skills/release-coherence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-coherence" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/release-coherence into .agents/skills/release-coherence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-coherence", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add macalbert/envilder --skill release-coherence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install macalbert/envilder release-coherence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/release-coherence .cursor/skills/release-coherence && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-coherence" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/release-coherence into .cursor/skills/release-coherence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-coherence", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/macalbert/envilder.git --path .github/skills/release-coherence--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add macalbert/envilder --skill release-coherence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install macalbert/envilder release-coherence --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/release-coherence .gemini/skills/release-coherence && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-coherence" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/release-coherence into .gemini/skills/release-coherence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-coherence", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install macalbert/envilder release-coherenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add macalbert/envilder --skill release-coherence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/release-coherence .github/skills/release-coherence && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-coherence" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/release-coherence into .github/skills/release-coherence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-coherence", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add macalbert/envilder --skill release-coherence -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install macalbert/envilder release-coherence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/release-coherence .opencode/skills/release-coherence && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-coherence" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/release-coherence into .opencode/skills/release-coherence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-coherence", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-coherence- GitHub stars
- 138
- Token cost
- ~1.3k tokens
- SKILL.md length
- 541 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Unified release coherence workflow for any component (CLI, GHA, or SDK).
- Works in 6 steps: Bump Version → Changelog Entry → ROADMAP Update (if applicable) → …
- Bumping a version
- SKILL.md covers When to Use, Components & Their Artifacts, Workflow and Quick Reference: Minimum…, plus 2 more sections
- Calls pnpm
What it does
Release Coherence is an agent skill from macalbert/envilder. Unified release coherence workflow for any component (CLI, GHA, or SDK). Use when bumping a version, preparing a release, or verifying that all documentation surfaces are updated after a version change. Orchestrates changelog, ROADMAP, website, and docs updates. Delegates to doc-maintenance, sdk-release-checklist, and doc-sync skills as needed.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes, Feature launches and release readiness and CI/CD. It works with Astro, Node.js, npm and Java. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.
When your agent uses it
- Bumping a version
- Preparing a release
- Verifying that all documentation surfaces are updated after a version change
Example prompts
- “/release-coherence”
Requirements
- Python 3
- Node.js
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Coherence loads about 1.3k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 541 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 541 words, ~1,331 tokens.
Download SKILL.mdSave it as
.claude/skills/release-coherence/SKILL.md (or your agent's skills folder).- name
- release-coherence
- description
- Unified release coherence workflow for any component (CLI, GHA, or SDK). Use when bumping a version, preparing a release, or verifying that all documentation surfaces are updated after a version change. Orchestrates changelog, ROADMAP, website, and docs updates. Delegates to doc-maintenance, sdk-release-checklist, and doc-sync skills as needed.
Release Coherence
Ensures all documentation surfaces stay aligned when releasing a new version of any component: CLI, GitHub Action, or SDK (any runtime).
When to Use
- Bumping a version of CLI, GHA, or any SDK
- After merging a feature/fix that warrants a changelog entry
- Before tagging a release to verify nothing was missed
- When asked to "prepare the release" for a component
Components & Their Artifacts
| Component | Version Source | Changelog | Web Surfaces |
|---|---|---|---|
| CLI | package.json (root) | docs/changelogs/cli.md | DocsContent (CLI section), README |
| GHA | package.json (root) | docs/changelogs/gha.md | DocsContent (GHA section), github-action/README.md |
| SDK .NET | src/sdks/dotnet/Envilder.csproj | docs/changelogs/sdk-dotnet.md | DocsContent, Sdks.astro, badge |
| SDK Python | src/sdks/python/pyproject.toml | docs/changelogs/sdk-python.md | DocsContent, Sdks.astro, badge |
| SDK Node.js | src/sdks/nodejs/package.json | docs/changelogs/sdk-nodejs.md | DocsContent, Sdks.astro, badge |
| SDK Go | src/sdks/go/ (tag) | docs/changelogs/sdk-go.md | DocsContent, Sdks.astro, badge |
| SDK Java | src/sdks/java/ (TBD) | docs/changelogs/sdk-java.md | DocsContent, Sdks.astro, badge |
Workflow
Step 1: Bump Version
Update the canonical version source file for the component.
Step 2: Changelog Entry
Add entry to docs/changelogs/{component}.md following doc-maintenance skill
format (categories: Added/Changed/Fixed/Documentation/Dependencies/Security).
Step 3: ROADMAP Update (if applicable)
Check ROADMAP.md for related items:
- Move completed features to appropriate status
- Update version references if roadmap tracks versions
- Skip if the release has no roadmap-tracked features
Step 4: Website Updates
For SDKs (delegate to sdk-release-checklist if new SDK)
- Version badge auto-updates via
astro.config.mjs(verify build picks it up) - Update DocsContent.astro if API changed (new methods, flags, options)
- Update Sdks.astro card if install command changed
- Update i18n keys if new strings added (
types.ts+en.ts,ca.ts,es.ts) - Changelog page sidebar already wired (no action for existing SDKs)
For CLI
- Update DocsContent.astro CLI section if new flags/options added
- Update
docs/pull-command.mdordocs/push-command.mdif behavior changed - Update root
README.mdif install or quick-start changed
For GHA
- Update DocsContent.astro GHA section if inputs changed
- Update
github-action/action.ymldescription/inputs - Update
github-action/README.mdanddocs/github-action.md
Step 5: Cross-Reference Check
- Root
README.mdreflects current capabilities - Examples in
examples/sdk/{runtime}/match current API - SDK README (
src/sdks/{runtime}/README.md) matches current API
Step 6: Validate
# Build website: verifies versions resolve and pages render
cd src/website && pnpm build
# Run doc-sync skill for comprehensive drift detection
# (or manually verify key surfaces)Delegate to doc-sync skill for full cross-surface audit if uncertain.
Quick Reference: Minimum Actions Per Component
Show full SKILL.md (217 more words)Show less
CLI / GHA release (no API change)
- Bump version in
package.json - Add changelog entry
- Done (website picks up version dynamically)
CLI / GHA release (with new flag/input)
- Bump version in
package.json - Add changelog entry
- Update docs (command reference, DocsContent)
- Update README
- Run
doc-sync
SDK release (no API change)
- Bump version in source file
- Add changelog entry
- Done (badge auto-updates via website build)
SDK release (with new API)
- Bump version in source file
- Add changelog entry
- Update SDK README
- Update examples
- Update DocsContent.astro section
- Update i18n if new strings
- Run
doc-sync
Delegation Map
| Need | Delegate to |
|---|---|
| How to write a changelog entry | doc-maintenance skill |
| Full SDK wiring (new SDK, not version bump) | sdk-release-checklist skill |
| Drift detection across all surfaces | doc-sync skill |
| Website i18n workflow | website-i18n skill |
| Website styling/components | website-design-system skill |
Anti-Patterns
| Anti-pattern | Correct approach |
|---|---|
| Hardcoding version in website HTML | Use __SDK_*_VERSION__ or __CLI_VERSION__ globals |
| Updating changelog but not docs | Always check if behavior/API changed → update docs |
| Updating website but not SDK README | Both must match: SDK README is source of truth for API |
| Skipping i18n for "minor" text changes | All 3 locales must stay in sync: TypeScript catches missing keys |
| Forgetting ROADMAP after completing a tracked feature | Check ROADMAP on every release |
© macalbert, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/release-coherence of macalbert/envilder.
Open the folder on GitHubat commit b6a0327
Compare with similar skills
Release Coherence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Coherence this skillmacalbert/envilder | 138 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Universal Project Release WorkflowJimLiu/baoyu-skills | 26k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Managing Python Releaseskajisho5/ffmpeg-skill | 1.9k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Dt Obs ServicesDynatrace/dynatrace-for-ai | 161 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| CI Pipeline Synthesizerkajisho5/ffmpeg-skill | 1.9k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Sap Btp Business Application Studiosecondsky/sap-skills | 460 | — | ~2.7k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Managing Python Releases
kajisho5/ffmpeg-skill
Manages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows.
Dt Obs Services
Dynatrace/dynatrace-for-ai
Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific telemetry for Java, .NET, Node.js, Python, PHP, and Go.
CI Pipeline Synthesizer
kajisho5/ffmpeg-skill
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.
Sap Btp Business Application Studio
secondsky/sap-skills
This skill provides comprehensive guidance for SAP Business Application Studio (BAS), the cloud-based IDE on SAP BTP built on Code-OSS.
Release Maintainer
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
More from macalbert/envilder
All 30 skills in this repoCode Review Perspectives
macalbert/envilder
Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.
Common Architecture Decisions
macalbert/envilder
Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.
Common Git
macalbert/envilder
Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.
Common Testing Conventions
macalbert/envilder
Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).
Doc Maintenance
macalbert/envilder
Workflow for maintaining changelogs, READMEs, and documentation files.
Doc Sync
macalbert/envilder
Audit and synchronize documentation across website, READMEs, and docs/.
Related
Questions about Release Coherence
What does Release Coherence do?
Unified release coherence workflow for any component (CLI, GHA, or SDK). Release Coherence is an agent skill from macalbert/envilder. Unified release coherence workflow for any component (CLI, GHA, or SDK).
When should I use Release Coherence?
Release Coherence fits situations like: bumping a version; preparing a release; verifying that all documentation surfaces are updated after a version change.
How do I install Release Coherence in Claude Code?
Run `npx skills add macalbert/envilder --skill release-coherence -a claude-code`. Or copy the skill folder (.github/skills/release-coherence in macalbert/envilder) into .claude/skills/release-coherence in your project. Claude Code loads it when a task matches its description.
How do I install Release Coherence in Codex?
Run `npx skills add macalbert/envilder --skill release-coherence -a codex`. Or copy the skill folder (.github/skills/release-coherence in macalbert/envilder) into .agents/skills/release-coherence in your project. Codex loads it when a task matches its description.
Can I use Release Coherence in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill release-coherence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-coherence, .gemini/skills/release-coherence, .github/skills/release-coherence and .opencode/skills/release-coherence in your project.
What does Release Coherence need to run?
Going by SKILL.md and its folder, Release Coherence needs the command-line tools its instructions call (pnpm). Our summary lists: Python 3; Node.js.
Does Release Coherence access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Coherence safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Coherence use?
Release Coherence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Coherence use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Coherence?
Skills that share tags, products or a category with Release Coherence: Universal Project Release Workflow (JimLiu/baoyu-skills, 26k stars), Managing Python Releases (kajisho5/ffmpeg-skill, 1.9k stars), Dt Obs Services (Dynatrace/dynatrace-for-ai, 161 stars) and CI Pipeline Synthesizer (kajisho5/ffmpeg-skill, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Coherence?
macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.
Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.