push

Stage changes, generate conventional commit messages, and push with automated rebase conflict resolution.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill push-cristoslc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/cristoslc/LLM-personal-agent-patterns/tree/main/L3-agents-core/.agents/skills/push
Command: npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill push-cristoslc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Committing and pushing changes involves repetitive manual steps: reviewing diffs, writing commit messages, staging files safely, and resolving rebase conflicts. This Skill automates the entire git commit-and-push workflow in one delegated operation. ## Core Features & Use Cases - Automated staging with secret detection: Identifies files like .env, *.pem, and credentials.* and excludes them from staging before committing. - Conventional commit message generation: Reads the staged diff and writes a commit message with a conventional-commit prefix (feat, fix, docs, chore, refactor, test) plus a Co-Authored-By trailer. - Non-interactive conflict resolution: During git pull --rebase, classifies conflicting files and prefers local changes for project files (docs/, src/, CLAUDE.md) or upstream for scaffolding files (.agents/, shared scripts), looping up to 10 iterations. - Use Case: After finishing a coding session with many modified files, invoke the skill to survey the working tree, commit everything with a descriptive message, rebase onto upstream, and push — without manually resolving routine conflicts. ## Quick Start Ask the agent to run the push skill to stage all current changes, commit them with a generated message, and push to the current branch's upstream.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automate git commit and push with generated commit messages?▼

Invoke the push skill, which surveys the working tree, stages changes, reads the staged diff to write a conventional-commit message, commits via heredoc, then pulls with rebase and pushes. It runs as a delegated sub-agent without pausing for confirmation.

How to resolve git rebase conflicts automatically?▼

The skill classifies each conflicting file: local changes win for project files like docs/, src/, and CLAUDE.md, while upstream wins for scaffolding like .agents/ and shared scripts. It loops rebase --continue up to 10 times, then aborts and asks the user if unresolved.

Does the push skill prevent committing secrets like .env files?▼

Yes. Before staging, it identifies files matching secret patterns such as .env, *.pem, *_rsa, credentials.*, and secrets.*, warns the user, and excludes them from staging either individually or via git reset after git add -A.

What commit message format does the push skill generate?▼

It generates a conventional-commit message with a prefix matching the dominant change type (feat, fix, docs, chore, refactor, test), an imperative subject line under 72 characters, a short why-focused body, and a Co-Authored-By trailer naming the model.

What happens if the current branch has no upstream tracking branch?▼

The skill checks for an upstream with git rev-parse @{u}. If none exists, it pushes using git push -u origin HEAD to set the upstream tracking branch automatically.