release-preplisted

# 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: 1. **Version**: "What version are you releasing? Or should I check the current version and suggest?" 2. **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>")