git:push

Run pre-flight checks, linting, and safety gates before pushing GitOps commits.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/ChanghwanK/dotfiles --skill git-push-changhwank
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git:push
Source: https://github.com/ChanghwanK/dotfiles/tree/main/claude/.claude/skills/git%3Apush
Command: npx skills add https://github.com/ChanghwanK/dotfiles --skill git-push-changhwank

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yamllint, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates a secure GitOps push workflow, ensuring that commits are validated, their deployment impact is analyzed, and safety gates are passed before being pushed to the remote repository.

Core Features & Use Cases

  • Pre-flight Checks: Validates current branch, upstream status, and uncommitted changes.
  • Linting & Impact Analysis: Runs yamllint and analyzes deployment impact using a Python script.
  • Safety Gates: Enforces manual confirmation for sensitive changes (e.g., production environments, deletions).
  • Rebase & Push: Integrates git pull --rebase before pushing to prevent conflicts.
  • Verification Plan: Generates a post-push verification checklist.
  • Use Case: After committing changes to a Kubernetes GitOps repository, use this Skill to push them safely, ensuring no unintended deployments occur and providing a clear verification plan.

Quick Start

Use the git:push skill to securely push your latest commits to the remote repository after ensuring all pre-flight checks and impact analyses are complete.

Frequently Asked Questions about git:push

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

FAQPage Schema
How do I push commits safely to a Kubernetes GitOps repository?▼

To push commits safely in a GitOps workflow, you need to perform pre-flight checks, run linting, analyze deployment impact, and pass safety gate confirmations before executing the remote push.

What is a secure GitOps push workflow?▼

A secure GitOps push workflow is a process that validates commits, analyzes their deployment impact, and enforces safety gates before pushing changes to prevent unintended production deployments.

How do I prevent unintended deployments when pushing GitOps changes?▼

You can prevent unintended deployments by enforcing manual safety gate confirmations for sensitive changes, such as production environment modifications or resource deletions, before executing the push.

Do I need yamllint and python3 to analyze deployment impact before pushing?▼

Yes, you need yamllint and python3 installed, because the deployment impact analysis and linting processes rely on these dependencies to validate configurations before pushing.

How do I avoid git conflicts when pushing to a remote GitOps repository?▼

To avoid conflicts when pushing to a remote GitOps repository, integrate a `git pull --rebase` step before executing the push to synchronize local commits with the upstream branch.

What should I do after pushing changes to a production GitOps environment?▼

After pushing changes to a production GitOps environment, you should follow a generated post-push verification plan to ensure deployment stability and confirm the applied changes.