ashaychangwani/imprint / .agents/skills/release
release
VerifiedCut a new semver release — bumps package.json, previews changelog, commits, tags, pushes, and verifies npm publish.
Release Skill
Cut a new release for Imprint. Follow these steps in order.
Step 1 — Determine bump type
Run git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline to see commits since the last tag.
Decide the bump type:
- major — breaking changes (
feat!:orBREAKING CHANGEin body) - minor — new features (
feat:) - patch — everything else (
fix:,refactor:,perf:,docs:,chore:, etc.)
If unsure, ask the user.
Step 2 — Read current version
Read package.json and extract the current version field.
Step 3 — Compute new version
Apply semver bump to the current version. For example: 0.1.0 + minor = 0.2.0.
Step 4 — Update package.json
Edit package.json to set the new version string. Do not change anything else.
Step 5 — Preview changelog
Run bunx git-cliff --config cliff.toml --unreleased --strip header and show the output to the user. Ask if it looks correct.
Step 6 — Commit
Stage and commit:
git add package.json
git commit -m "chore(release): v<VERSION>"
Use the exact version string. No Co-Authored-By trailer for release commits.
Step 7 — Tag
git tag v<VERSION>
Step 8 — Push
Ask the user for confirmation, then:
git push && git push --tags
This triggers the release.yml workflow, which creates the GitHub Release, publishes the npm package, and uploads binaries.
Step 9 — Watch publish
Watch the release workflow:
gh run list --workflow release.yml --limit 1
gh run watch <RUN_ID> --exit-status
Then verify npm:
npm view imprint-mcp version
If GitHub Actions cannot publish and local npm auth is available, publish manually from the tagged commit:
npm whoami
npm publish --access public
Step 10 — Confirm
Tell the user: "Release v<VERSION> tagged and pushed. GitHub Actions created the release at https://github.com/ashaychangwani/imprint/releases, and npm shows imprint-mcp@<VERSION>."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |