How do I install the Release Preflight skill?

Run npx skillmds@latest add fabioc-aloha/release-preflight-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Release Preflight skill do?

Pre-checks, version consistency, and deployment discipline. It is listed under Coding & Dev Tools on SkillMD.

Is Release Preflight safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Preflight?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Preflight free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Preflight?

fabioc-aloha (@fabioc-aloha) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Preflight by fabioc-aloha — Agent Skill

Name: Release Preflight
Author: fabioc-aloha

File contents

Release Preflight Skill

Pre-checks, version consistency, and deployment discipline.

The Golden Rule

NEVER publish without running the preflight checklist.

Quick Start

# Full preflight check
node scripts/release-preflight.cjs

# With packaging test
node scripts/release-preflight.cjs

# Skip time-consuming tests
node scripts/release-preflight.cjs

Version Locations (Must Stay Synchronized)

#	Location	Field	Example
1	`heir/platforms/vscode-extension/package.json`	`version`	`"8.2.1"`
2	`heir/CHANGELOG.md`	Latest heading	`## [8.2.1] - 2026-04-22`
3	`BUILD-MANIFEST.json` (if present)	`version`	`"8.2.1"`
4	Git tag	Tag name	`v8.2.1`

Preflight Gates

Gate	Check	Script Flag
0	PAT configured	Always
1	Version sync (all 7 locations)	Always
2	VSIX exists	Always
3	Git clean	Always
4	Git tag available	Always
5	VSCE_PAT available	Always
6	Heir sync drift	Always

Full Release Workflow

# VS Code Extension release
node scripts/release-vscode.cjs

# M365 Agent release
node scripts/release-m365.cjs --validate

Version Bump Only

# 1. Bump
npm version patch --no-git-tag-version

# 2. Get version
$v = (Get-Content package.json | ConvertFrom-Json).version

# 3. Update CHANGELOG, commit, tag, push
git add -A; git commit -m "release: v$v"; git tag "v$v"; git push --tags

Common Mistakes

Mistake	Prevention
Published without version bump	Run preflight first
CHANGELOG not updated	Script checks this
Forgot to push tags	Script does this
Version mismatch	Grep entire repo for old version
PAT 401 error	Refresh PAT before release

Related Scripts

Script	Purpose
`scripts/release-preflight.cjs`	Pre-release validation
`scripts/release-vscode.cjs`	Full VS Code release
`scripts/release-m365.cjs`	M365 agent packaging

Triggers

"release", "publish", "deploy"
"preflight", "pre-release check"
"version bump", "version sync"

Scripts: scripts/release-preflight.cjs, scripts/release-vscode.cjs

---name: release-preflight-2description: Pre-checks, version consistency, and deployment discipline.---# Release Preflight Skill> Pre-checks, version consistency, and deployment discipline.## The Golden Rule> **NEVER publish without running the preflight checklist.**## Quick Start```bash# Full preflight checknode scripts/release-preflight.cjs# With packaging testnode scripts/release-preflight.cjs# Skip time-consuming testsnode scripts/release-preflight.cjs```## Version Locations (Must Stay Synchronized)| # | Location | Field | Example || --- | ------------------------------------------------------------ | ------------------- | ------------------------- || 1 | `heir/platforms/vscode-extension/package.json` | `version` | `"8.2.1"` || 2 | `heir/CHANGELOG.md` | Latest heading | `## [8.2.1] - 2026-04-22` || 3 | `BUILD-MANIFEST.json` (if present) | `version` | `"8.2.1"` || 4 | Git tag | Tag name | `v8.2.1` |## Preflight Gates| Gate | Check | Script Flag || ---- | ------------------------------ | ----------- || 0 | PAT configured | Always || 1 | Version sync (all 7 locations) | Always || 2 | VSIX exists | Always || 3 | Git clean | Always || 4 | Git tag available | Always || 5 | VSCE_PAT available | Always || 6 | Heir sync drift | Always |## Full Release Workflow```bash# VS Code Extension releasenode scripts/release-vscode.cjs# M365 Agent releasenode scripts/release-m365.cjs --validate```## Version Bump Only```powershell# 1. Bumpnpm version patch --no-git-tag-version# 2. Get version$v = (Get-Content package.json | ConvertFrom-Json).version# 3. Update CHANGELOG, commit, tag, pushgit add -A; git commit -m "release: v$v"; git tag "v$v"; git push --tags```## Common Mistakes| Mistake | Prevention || ------------------------------ | -------------------------------- || Published without version bump | Run preflight first || CHANGELOG not updated | Script checks this || Forgot to push tags | Script does this || Version mismatch | Grep entire repo for old version || PAT 401 error | Refresh PAT before release |## Related Scripts| Script | Purpose || --------------------------------------------- | -------------------------------------- || `scripts/release-preflight.cjs` | Pre-release validation || `scripts/release-vscode.cjs` | Full VS Code release || `scripts/release-m365.cjs` | M365 agent packaging |## Triggers- "release", "publish", "deploy"- "preflight", "pre-release check"- "version bump", "version sync"---_Scripts: `scripts/release-preflight.cjs`, `scripts/release-vscode.cjs`_

Frequently asked questions

Release Preflight