repo-release-tools

Teaches AI assistants (Claude Code, Claude Desktop, Cursor) how to install and connect the repo-release-tools MCP server so rrt tools (config, version, health, drift, tree, artifacts, changelog, validation) are available via MCP. Use when wiring up rrt[mcp] to an AI assistant for the first time. DO NOT USE for debugging rrt CLI commands or for users who only need the CLI.

Helps rrt users bootstrap install targets, local workflow checks, and day-one automation safely. Use when setting up rrt in a new repository or workstation. DO NOT USE for repo-maintainer-only automation changes or for cloning `.claude/*` runtime assets into source control.

Helps rrt users create, validate, and repair semantic branch names that match their workflow. Use when starting or renaming work with `rrt branch`. DO NOT USE for arbitrary git branching conventions unrelated to rrt.

Helps rrt users keep `[Unreleased]` current with less manual changelog work. Use when deciding between automated and manual changelog flows with rrt hooks. DO NOT USE for maintainers redesigning changelog internals or section mapping.

Helps rrt users run local preflight checks that mirror common CI gates for branch, changelog, docs, and release readiness. Use when you want fewer CI surprises before opening a PR. DO NOT USE for editing CI pipeline internals.

Helps rrt users write conventional commits with clear intent and fewer rejected commits. Use when shaping commit messages or triaging commit lint failures. DO NOT USE for changelog authoring without a commit-quality decision.

Helps rrt users validate config files, version targets, and install paths before policy failures happen. Use when setting up or repairing rrt config. DO NOT USE for changing internal config loader implementation.

Helps rrt users keep generated docs, command references, and source-owned docs aligned. Use when docs drift from command behavior or source assets change. DO NOT USE for long-form product writing unrelated to rrt automation.

Helps rrt users migrate from `uvx --from repo-release-tools ...` one-off usage to an installed workflow with local or global assets. Use when moving from zero-install experimentation to a maintained setup. DO NOT USE for package publishing or maintainers changing installer internals.

Helps rrt users run a safer release flow from dry-run planning through readiness checks and final bump execution. Use when preparing a release with changelog and version validation. DO NOT USE for maintainers changing GitHub Action internals.

Guides rrt users through version bumps, semver decisions, and version target previews. Use when planning or applying a release bump with rrt. DO NOT USE for manual version-file surgery or for repository-maintainer-only release tooling changes.