deploy-code-changes

Run pre-commit hooks, commit, push to origin/main, and trigger scripts/deploy.py.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/dariosky/carun --skill deploy-code-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-code-changes
Source: https://github.com/dariosky/carun/tree/main/skills/deploy-code-changes
Command: npx skills add https://github.com/dariosky/carun --skill deploy-code-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates a safe, auditable flow to deploy current repository changes from main, including pre-commit checks, selecting a concise commit message from the diff, pushing to origin/main, and triggering production deployment.

Core Features & Use Cases

  • Enforces a main-branch deployment workflow with pre-commit validation, diff review, and automated messaging.
  • Commits, pushes, and deploys changes in a single, auditable operation.
  • Suitable for releasing production-ready updates in monorepos or multi-component projects.

Quick Start

Start the deployment from the repository root to publish the latest changes to production.

Frequently Asked Questions about deploy-code-changes

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

FAQPage Schema
How do I automate git deployment from main with pre-commit hooks?

Automating git deployment from main involves running pre-commit hooks, generating a commit message from the diff, committing, pushing to origin/main, and triggering a deployment script. This workflow ensures changes are validated and deployed safely.

What is the safest way to deploy code changes from a Git repository to production?

The safest way to deploy code changes from a Git repository to production is enforcing a main-branch workflow with pre-commit validation, diff inspection, and automated commit messaging before triggering the deployment script. This prevents unreviewed code from reaching production.

Can I force push to origin/main during an automated deployment workflow?

Yes, the automated deployment workflow supports forced pushes to origin/main. It also allows explicit commit messaging and diff inspection to maintain control over the repository state before the deployment script is triggered.

Does the deployment workflow support a dry-run mode for validating changes?

Yes, the deployment workflow includes an optional dry-run mode for validation. This allows you to inspect the diff and run pre-commit checks without actually committing, pushing, or triggering the production deployment script.

Do I need a custom deploy.py script to use this automated deployment workflow?

Yes, the workflow automatically invokes scripts/deploy.py to trigger production deployment after pushing to origin/main. You must provide this deployment script in your repository to complete the automated release process.