deploy

Commits all changes, pushes to the remote, and confirms deployment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the repetitive manual steps of reviewing changes, staging files, writing commit messages, committing, and pushing code every time you want to ship work. ## Core Features & Use Cases - Change Review: Runs git status and git diff to inspect staged and unstaged changes before committing. - Safe Staging: Stages specific files and never includes .env files, credentials, or .bak files. - Commit and Push: Uses your provided message or writes a concise one, appends a Claude co-author trailer, pushes, and reports the commit hash. - Use Case: After finishing a feature, invoke the skill with a commit message to review, commit, and push everything in one step. ## Quick Start Ask the assistant to deploy the current changes with the commit message "add user login endpoint".

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I commit and push all changes in one step?

Invoke the deploy skill, optionally with a commit message. It reviews git status and diff, stages the relevant files, commits with your message or a generated summary, pushes to the remote, and reports the commit hash.

What happens if there are no changes to deploy?

The skill checks git status first. If there are no modified or untracked files, it reports "Nothing to deploy" and stops without creating an empty commit.

Does the deploy skill stage .env or credential files?

No. It stages specific filenames rather than using git add -A, and explicitly never stages .env files, credentials, or .bak files to avoid leaking secrets.

Can I provide my own commit message when deploying?

Yes. Pass your message as the skill argument and it will be used verbatim. If omitted, the skill writes a concise message summarizing the diff, always ending with a Claude co-author trailer.

Why did my deploy not push to the remote?

Push failures usually come from rejected non-fast-forward updates, missing remote permissions, or network issues. Pull and reconcile the remote branch first, then re-run the deploy.