deploy

Automate Node.js production deployment with Git merge and PR creation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bselee/MuRP --skill deploy-bselee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/bselee/MuRP/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/bselee/MuRP --skill deploy-bselee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end deployment workflow, reducing manual steps and human error when pushing changes to production.

Core Features & Use Cases

  • Build & Validate: Run builds to catch errors before deployment.
  • Version Control & Push: Ensure changes are committed and pushed to the current branch.
  • Deployment Orchestration: Merge into the claude/merge-to-main branch and trigger deployment to production.
  • Use Case: When finishing a feature, trigger a one-click deployment that builds, merges to the deployment branch, and deploys automatically.

Quick Start

Use this skill to push your current branch to main and deploy to production by merging into claude/merge-to-main.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate deployment of Node.js projects to production?

Automate deployment by running builds, committing changes, and merging into a deployment branch that triggers production release. This Skill handles the entire end-to-end workflow—build validation, Git commits, pushes, cross-branch merges, and PR creation—reducing manual steps and human error in your CI/CD pipeline.

Can I use this with my existing Git workflow and npm build process?

Yes. This Skill integrates with Node.js projects using Git-based workflows. It runs npm build, executes Git commands (status, log, add, commit, push), and performs merges into claude/merge-to-main, assuming npm and Git are available in your repository.

What happens when I trigger a deployment?

The Skill builds your code, checks Git status, commits and pushes changes, merges into the deployment branch, and creates a pull request that publishes a release. You receive a PR URL and deployment status confirming the production deployment completed.

Do I need repository access and specific branch setup to deploy?

Yes. You need Git repository access, npm configured for builds, and the claude/merge-to-main branch in place for merges. The Skill requires permissions to commit, push, and create pull requests to function end-to-end.

When should I use automated deployment instead of manual Git commands?

Use automation when finishing features and pushing to production. It eliminates repeating build, commit, push, and merge steps manually, ensures consistent deployment processes, and catches build errors before production without requiring individual Git commands.

What's the difference between pushing to my current branch versus deploying?

Pushing commits changes to your current branch; deployment goes further by merging into claude/merge-to-main and triggering a production release with PR creation. This Skill combines both: it pushes your branch, then orchestrates the merge and deployment steps automatically.