push

Push code to remote repositories with safety checks and CI/CD verification.

Updated May 16, 2026

Search Tags:#code quality #git #CI/CD #safety checks #code push

Ready to run

npx skills add https://github.com/korchasa/flowai-plugins --skill push-korchasa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: push
Source: https://github.com/korchasa/flowai-plugins/tree/main/plugins/flowai/skills/push
Command: npx skills add https://github.com/korchasa/flowai-plugins --skill push-korchasa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures secure and controlled code pushes, preventing unauthorized force pushes and handling diverged branches safely, while integrating with CI/CD processes.

Core Features & Use Cases

Safety Checks: Prevents force pushes and confirms before setting first-time upstream and pushing to protected branches.
CI/CD Integration: Waits for CI/CD runs to complete and handles failures by handoff to the investigate skill.
Use Case: When you want to push code to a remote repository, this Skill will handle the push with all necessary checks and then wait for the CI/CD process to complete, ensuring that your code quality is maintained.

Quick Start

Execute the flowai:push command to push your current branch to the remote repository, with all safety checks and CI/CD integration applied.

Frequently Asked Questions about push

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

FAQPage Schema

How do I prevent accidental force pushes to protected git branches?▼

Preventing accidental force pushes to protected git branches requires explicit user authorization checks before proceeding. The Skill intercepts force push commands and prompts for confirmation, also warning when setting first-time upstream tracking on diverged branches.

How does git push integrate with CI/CD pipelines for code quality verification?▼

Git push integration with CI/CD pipelines waits for verification runs to complete after pushing code. If the CI/CD process fails, the Skill hands off investigation to specialized tools to maintain your code quality.

What is the best way to handle diverged branches when pushing code to a remote repository?▼

Handling diverged branches when pushing code to a remote repository requires safety checks to prevent overwriting remote changes. The Skill detects branch divergence and ensures explicit authorization before proceeding with destructive push operations.

Do I need git installed locally to run automated safety checks before pushing code?▼

You need git installed locally to run automated safety checks before pushing code. The Skill requires git for local repository interaction to verify branch status and execute secure pushes with CI/CD integration.

Why does my code push fail safety checks when the upstream branch is not set?▼

Your code push fails safety checks when the upstream branch is not set because the Skill confirms before setting first-time upstream tracking. This prevents accidentally pushing to unintended remote branches.