dev-release
Provides a guided, step-by-step automation workflow for managing software releases and deployments.
Install
mkdir -p .claude/skills/dev-release-forecast-bio && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12234" && unzip -o skill.zip -d .claude/skills/dev-release-forecast-bio && rm skill.zipInstalls to .claude/skills/dev-release-forecast-bio
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use to drive a guided release pipeline — version bump, changelog drafting, doc review, test/lint, PR creation, tag, GitHub release, and back-merge. Mixes agent steps (the agent does them) with user-only steps (push / merge / tag, blocked by policy and printed for the user). Trigger when the user says "cut a release", "release v0.6", "/dev-release", or asks to bump version + changelog + tag.Key capabilities
- →Determine the source and target branches for the release.
- →Bump the project version in configuration files like Cargo.toml or package.json.
- →Draft a changelog by categorizing commits since the last tag.
- →Review documentation for outdated feature descriptions and report gaps.
- →Run project-specific tests and linters, fixing lint issues automatically.
- →Create a pull request with a changelog summary and test results.
How it works
The skill guides a user through a release flow by executing agent steps and providing exact commands for user-only steps like Git pushes or merges. It detects project types to apply appropriate version bumps, changelog generation, and test/lint commands.
Inputs & outputs
When to use dev-release
- →Cutting a project release
- →Managing version bumps
- →Automating release check-lists
About dev-release
Orchestrates release steps including versioning, changelog drafting, test/linting, PR generation, and GitHub release finalization.
Use to drive a guided release pipeline — version bump, changelog drafting, doc review, test/lint, PR creation, tag, GitHub release, and back-merge. Mixes agent steps (the agent does them) with user-only steps (push / merge / tag, blocked by policy and printed for the user). Trigger when the user say
When not to use it
- →When the user needs to manually push, merge, or tag without agent guidance.
- →When the project is not a Git repository.
- →When the user wants to amend existing commits or force-push.
Limitations
- →The agent cannot run git push, git merge, or git tag commands.
- →The agent cannot amend existing commits.
- →The agent cannot force-push.
How it compares
This skill automates the detection of project types and the execution of specific commands for versioning, changelog generation, and testing, whereas a manual approach would require the user to identify these details and run commands indivi
Compared to similar skills
dev-release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dev-release (this skill) | 0 | 4mo | Review | Intermediate |
| release | 0 | 3mo | No flags | Advanced |
| gcp-cloud-run | 5 | 7mo | Review | Intermediate |
| flow-nexus-platform | 6 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by forecast-bio
View all by forecast-bio →You might also like
release
adpigft
Prepare release readiness evidence, release notes, rollback, monitoring, risks, and approvals.
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.