Release prep

Skill Smart-AI-Memory/attune-ai/.agents/skills/release-prep

Pre-release preparation with health checks, security audit, changelog validation, version bumps, and dependency audits. Triggers on: release, publish, ship, deploy, version bump, changelog.From its SKILL.md

Install

npx -y skills add Smart-AI-Memory/attune-ai --skill release-prep

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, as published. Nobody here has run it

Release Prep

IMPORTANT: Start your response with a context preamble.

Call help_lookup(topic="release-prep", mode="preamble") and display the returned preamble text as a blockquote. Then tell the user they can say "tell me more" for a step-by-step guide, or answer the scoping questions below to proceed.

If the MCP call fails, fall back to:

Release Prep — Runs pre-release checks — health, security, changelog, and go/no-go assessment.

Scoping

Before running, ask:

Version: "What version are you releasing? Or should I check the current version and suggest?"
Scope: "Full advisory or a specific check?"
- Full: advisory across security, testing, docs, versioning
- Specific: Single check (e.g., just changelog)

MCP Tools

Tool	What It Does
`release_notes`	Changelog draft + go/no-go advisory (single-agent SDK)
`health_check`	Project health score (tests + lint + coverage)
`dependency_check`	Dependency audit and vulnerability scan
`secure_release`	Full release pipeline with security gates

Advisory vs gate. release_notes is advisory — it drafts a changelog and gives a recommendation, it does not block. The deterministic 4-agent gate (real bandit/ruff/pytest + hard thresholds) is CLI-only: attune workflow run release-gate.

Execution

Call the release_notes MCP tool for a changelog draft and go/no-go recommendation:

release_notes(path="<project root>")

For targeted checks, use individual tools:

health_check(path="<project root>")
dependency_check(path="<project root>")
secure_release(path="<project root>")

The full release prep covers four areas:

Security — scans for vulnerabilities that block release
Testing — checks test coverage, identifies gaps
Documentation — validates changelog, README, and documentation freshness
Versioning — checks version bumps, dependency compatibility, semver compliance

Output Format

## Release Readiness Report

**Verdict:** READY / NOT READY
**Version:** X.Y.Z → A.B.C
**Date:** YYYY-MM-DD

### Agent Reports

#### Security
- Status: PASS / FAIL
- Issues: [list if any]

#### Testing
- Coverage: X%
- Missing tests: [list if any]

#### Documentation
- Changelog: UP TO DATE / NEEDS UPDATE
- README: CURRENT / STALE

#### Versioning
- Semver: VALID / INVALID
- Breaking changes: YES / NO
- Dependencies: ALL COMPATIBLE / [list conflicts]

### Blockers
| Blocker | Agent | Severity |
|---------|-------|----------|

### Recommendations
1. [Ordered list of actions before release]

Help

After presenting results, call:

help_lookup(topic="release-prep", mode="workflow_help")

If templates are returned, offer: "I have tips about release preparation — want to see them?"

Follow-Up

After presenting results, offer:

"Want me to fix the blockers?"
"Should I update the changelog?"
"Ready to tag and publish?"