push-to-production
Handles end-to-end production deployment, including versioning, releases, and issue tracking.
Install
mkdir -p .claude/skills/push-to-production && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13271" && unzip -o skill.zip -d .claude/skills/push-to-production && rm skill.zipInstalls to .claude/skills/push-to-production
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.
Release to production by pushing to main and release branches, verifying Railway auto-deploy, creating a GitHub Release, and transitioning Linear issues. Use when user says "push to production", "release", "deploy to production", or "ship it". Bumps version, updates changelog, pushes to main + release, verifies Railway deployment, creates GitHub Release, and moves Linear issues to Released.Key capabilities
- →Verify Linear MCP availability and record Done issues
- →Check current Git branch, working tree, and remote synchronization
- →Read PLANS.md for incomplete tasks
- →Run verifier agent to confirm build and tests pass
- →Assess changes by examining commits since the last tag
- →Determine semantic version bump based on commit types
How it works
The skill performs pre-flight checks on the Git repository, Linear issues, and project plans, then determines the next version based on commit history. It generates a changelog entry and prepares for pushing to production branches and creating a GitHub Release.
Inputs & outputs
When to use push-to-production
- →Releasing to production
- →Managing github releases
- →Updating linear issues
About push-to-production
Releases to production by pushing to branches, triggering Railway deploys, creating GitHub Releases, and transitioning Linear issues to Done. It ensures a standardized release flow.
Release to production by pushing to main and release branches, verifying Railway auto-deploy, creating a GitHub Release, and transitioning Linear issues. Use when user says "push to production", "release", "deploy to production", or "ship it". Bumps version, updates changelog, pushes to main + relea
When not to use it
- →When not on the 'main' branch
- →When the working tree has uncommitted changes
- →When the local branch is behind the remote
Limitations
- →It stops if the Git branch is not 'main' or the working tree is dirty.
- →It stops if the verifier agent reports build or test failures.
- →It stops if there are incomplete tasks in PLANS.md.
How it compares
This skill automates a multi-step production release process, including versioning, changelog generation, and GitHub Release creation, ensuring adherence to predefined rules and checks.
Compared to similar skills
push-to-production side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| push-to-production (this skill) | 0 | 3mo | Review | Intermediate |
| agent-workflow-automation | 4 | 7mo | Review | Advanced |
| project-os | 1 | 8mo | Review | Intermediate |
| project-tooling | 1 | 5mo | Caution | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
agent-workflow-automation
ruvnet
Agent skill for workflow-automation - invoke with $agent-workflow-automation
project-os
Peiiii
AI project OS for autonomous loop, automated orchestration, and rule-driven execution.
project-tooling
alinaqi
gh, vercel, supabase, render CLI and deployment platform setup
release-version
corvo007
Use when releasing a new version - guides through version bump, changelog generation, commit grouping, tagging, and GitHub CI tracking. Triggers on "发布新版本", "release", "发版", or version release requests.
Release
tobagin
Create a new Keymaker release — analyze changes, bump version, update changelog/README/AppStream metadata, build, commit, tag, push, and create GitHub release
release
RajwanYair
Bump the version, update the changelog, tag, and publish a GitHub release for RegiLattice. Use when preparing a new release, updating version numbers, creating a CHANGELOG entry, or pushing a version tag to trigger the CI release workflow. Triggers on: 'bump version', 'release', 'publish', 'version'