Create a changeset entry to document a version bump and changelog for the current changes
Scanned 9/7/2026
Install to Claude Code
Skills Directorynpx -y skills add jiayaoqijia/cryptoskill --skill alchemy-mcp --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Alchemy Mcp?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jiayaoqijia-alchemy-mcp)More formats (shields.io, HTML) on the badges page.
---
name: changeset
description: Create a changeset entry to document a version bump and changelog for the current changes
disable-model-invocation: true
argument-hint: "[patch|minor|major] [description]"
---
Create a changeset entry for the current branch's changes.
## Instructions
1. Run `git diff main...HEAD --stat` and `git log main..HEAD --oneline` to understand what changed on this branch.
2. If no argument was provided, analyze the changes to determine:
- **Bump type**: `patch` for fixes, `minor` for new features, `major` for breaking changes
- **Summary**: A concise description of the change for the changelog
3. If `$ARGUMENTS` was provided, parse it as `[bump] [description]` (e.g., `minor Add changeset-based release workflow`).
4. Create a new markdown file in `.changeset/` with a random lowercase-kebab-case name (e.g., `.changeset/cool-birds-fly.md`) using this exact format:
```
---
"@alchemy/mcp-server": <bump>
---
<description>
```
Where `<bump>` is `patch`, `minor`, or `major` and `<description>` is the changelog entry.
5. Show the user the created changeset file and ask if they'd like to adjust anything.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
