| name | release-prep |
| description | Guides the pre-release process for the dev-team-agents repository. Runs consistency checks, validates README sync, determines the correct version bump, and creates the git tag. Use before any version tag is created. |
Release Prep
This skill guides the release process for this repository. It orchestrates existing scripts and enforces the rules defined in CLAUDE.md § Versioning.
Source of truth for versioning rules: CLAUDE.md § Versioning.
When to Use
Invoke this skill before creating any vX.Y.Z git tag. Do not tag directly — always run through this checklist first.
Step 0 — Present the Release Plan
Before running any checks, present a plan with:
- Proposed version bump (major / minor / patch) and rationale
- List of validation steps to execute
- Any known risks or items that may block the release
State explicitly: "Awaiting your approval before proceeding."
Step 1 — Determine the Version Bump
Read the commits since the last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Apply the rules from CLAUDE.md § Versioning:
| Change type | Bump |
|---|
| Agent behavior changes, removed skills, breaking install changes | major |
| New agents or new skills | minor |
| Fixes, clarifications, doc updates, script patches | patch |
If commits span multiple categories, apply the highest bump that applies.
Get the current version:
git describe --tags --abbrev=0
Calculate the next version and confirm with the user before proceeding.
Step 2 — Orphan Skill Scan
bash helpers/orphan-skill-scan.sh
- AUTO-FIXED lines: verify the affected agent still reads correctly
- ACTION REQUIRED lines: resolve before continuing — do not tag with orphaned skills
Step 3 — Agent Compliance Check
Run the linter — it enforces the frontmatter contract (name, description, tier, model), the skill identity rules, the quiz-first rule, and the model↔tiers.json↔run-banner drift guard:
bash helpers/agent-lint.sh
Then verify by hand what the linter does not cover:
bash helpers/size-limits.sh
The agent ceiling is 205: 200 lines of content plus the fixed 5-line run-banner block. Anything approaching it should move reference material into a skill — do not raise the ceiling to make an agent fit.
Step 4 — README Sync Check
The rule from CLAUDE.md: any change to README.md must be reflected in README.pt-BR.md in the same commit.
Check if they diverged since the last tag:
git diff $(git describe --tags --abbrev=0)..HEAD -- README.md README.pt-BR.md
If README.md changed but README.pt-BR.md did not (or vice versa), stop and sync them before continuing.
Step 5 — Verify Package Exclusions
The install script strips CLAUDE.md, scripts/install.sh, and the entire helpers/ directory from the tarball. Confirm exclusions are still in place:
grep -n "CLAUDE.md\|helpers\|install.sh" scripts/install.sh
Expected: at least one line per file referencing exclusion from the extracted content.
Step 6 — Validate User-Invocable Skills Table
For each entry in the § User-Invocable Skills table in CLAUDE.md, verify the skill file exists:
ls skills/skill-creator/SKILL.md
ls .claude/skills/agent-creator/SKILL.md
If any file is missing, stop — do not tag until the table and the filesystem are in sync.
Step 7 — Auto-Docs and Language Check
Review commits since the last tag for:
- Observable behavior changes (new agent/skill, renamed file, changed install flow, new script flag) →
README.md and README.pt-BR.md must be updated. If not, update before tagging.
- Language → scan new/modified
.md files for non-English content (except intentional exceptions). Flag any violations.
git diff $(git describe --tags --abbrev=0)..HEAD --name-only | grep "\.md$"
Step 9 — Create the Tag
After all checks pass:
git add -p
git tag -a vX.Y.Z -m "Release vX.Y.Z"
git push origin vX.Y.Z
Confirm the tag is visible:
git describe --tags
Rollback Reference
If a tag was pushed incorrectly:
git tag -d vX.Y.Z
git push origin :refs/tags/vX.Y.Z
Do not run the remote delete without explicit user confirmation.
