菜单
Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release |
| description | Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version". |
Cut a new release for the ra-mcp project.
Determine current state — run these in parallel:
git tag --sort=-v:refname | head -5 to find the latest taggrep '^version' pyproject.toml | head -1 to find the current versiongit log --oneline $(git describe --tags --abbrev=0)..HEAD to list commits since the last tagDecide the version bump — follow semver based on conventional commits:
fix, refactor, perf, docs, style, test, build, ci, chorefeat commit! or BREAKING CHANGE footerConfirm with the user — show:
Cut the release — run:
make release VERSION=<version>
This bumps pyproject.toml, commits, tags, and pushes. The tag push
triggers two CI workflows in parallel: release.yml (changelog + GitHub
Release) and publish.yml (Docker build, push, sign, and attestations).
Monitor CI workflows — after the tag push, watch both workflows:
gh run list --limit 5 to find the triggered runsgh run view <run-id> until both "Release" and "Publish"
workflows complete (check every ~30 seconds)gh run view <run-id> --log-failed to
get the error details and report them to the userReport — confirm the tag was pushed and link to the GitHub releases page:
https://github.com/AI-Riksarkivet/ra-mcp/releases
make release.claude/commands/commit.md —
in particular: no co-author lines, no Claude attribution, clean
conventional commit formatScaffold a new MCP workspace package under packages/. Covers directory structure, pyproject.toml, tools.py, server.py, tool registration, formatter, __init__.py, tests, root server wiring, and uv sync. Use when: add new MCP package, new workspace, new tool server, scaffold package, add module.
This skill should be used when the user asks to "add an app to my MCP server", "add UI to my MCP server", "add a view to my MCP tool", "enrich MCP tools with UI", "add interactive UI to existing server", "add MCP Apps to my server", or needs to add interactive UI capabilities to an existing MCP server that already has tools. Provides guidance for analyzing existing tools and adding MCP Apps UI resources.
This skill should be used when the user asks to "add MCP App support to my web app", "turn my web app into a hybrid MCP App", "make my web page work as an MCP App too", "wrap my existing UI as an MCP App", "convert iframe embed to MCP App", "turn my SPA into an MCP App", or needs to add MCP App support to an existing web application while keeping it working standalone. Provides guidance for analyzing existing web apps and creating a hybrid web + MCP App with server-side tool and resource registration.
Python design patterns and anti-patterns. Use when designing new components, refactoring, reviewing code for common mistakes, choosing abstractions, or evaluating pull requests for structural issues like tight coupling, leaking internal types, or error handling problems.
Modern Python type safety with type hints, generics, protocols, and strict type checking using ty and ruff. Use when adding type annotations, implementing generic classes, defining structural interfaces, configuring ty/ruff, or writing type-safe Python 3.13+/3.14+ code. Triggers on mentions of type hints, typing, TypeVar, Protocol, overload, TypeIs, Pydantic models, ty check, ruff type rules, or any static type analysis in Python.
MCP Apps guide: FastMCP 3.4+ server, Svelte 5 view, tool visibility, polling, sizing, fullscreen, view persistence. Use for any MCP App/UI work.