commit-push-deploy

Commits code changes, pushes to remote, and deploys to production. Use when the user wants to commit, push, and deploy their changes in one workflow.

⭐944stars🔀44forks📁View on GitHub🕐Updated Jan 8, 2026

When & Why to Use This Skill

This Claude skill automates the end-to-end software delivery pipeline by integrating build verification, Git version control, and production deployment into a single, streamlined workflow. It enhances developer productivity by ensuring code quality through pre-commit builds and managing the entire lifecycle from local changes to live production updates with built-in approval gates.

Use Cases

  • Streamlining the release process for web applications by automating the build, push, and deployment steps in one sequence.
  • Ensuring code stability by enforcing mandatory build checks before any code is committed to the repository.
  • Simplifying Git workflows for developers by automatically staging changes and drafting commit messages for quick review and approval.
  • Reducing manual errors during production deployments by using standardized deployment scripts and automated remote synchronization.
namecommit-push-deploy
descriptionCommits code changes, pushes to remote, and deploys to production. Use when the user wants to commit, push, and deploy their changes in one workflow.

Commit, Push, and Deploy

Instructions

When the user invokes this skill, follow these steps:

1. Build first

Run the build to ensure the code compiles without errors before committing:

cd diffusion-explorer/apps/rectified-flow-explainer && npm run build

If the build fails, stop and report the errors to the user.

2. Stage and review changes

git add -A
git status
git diff --staged

3. Generate commit message and ask for approval

Draft a commit message based on the staged changes. Present the commit message to the user and ask for their approval before proceeding. Use the AskUserQuestion tool to get confirmation.

4. Commit

Once approved, commit with the message:

git commit -m "<approved message>"

5. Push

Push to the remote repository:

git push

6. Deploy

Run the deploy script directly (without rebuilding since we already built in step 1):

cd diffusion-explorer/apps/rectified-flow-explainer && node scripts/deploy.js

This deploys the built files to the production website.

Notes

  • Always build before committing to catch errors early
  • Use node scripts/deploy.js instead of npm run deploy to avoid a redundant rebuild
  • The deploy script clones the main website repo, copies the build, and pushes the changes