Git-Commit-Push

Commit and push code with pre-push validations and main merge.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production --skill git-commit-push-paulinett1508-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git-Commit-Push
Source: https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production/tree/main/.claude/skills/git-commit-push
Command: npx skills add https://github.com/paulinett1508-dev/SuperCartolaManagerv5-production --skill git-commit-push-paulinett1508-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken or incomplete releases by automating commit creation, enforcing pre-push validations, and confirming that the local repo, GitHub main, and the VPS Docker deployment are actually synchronized.

Core Features & Use Cases

  • Structured commit generation (Conventional Commits): Builds descriptive commit messages from the detected diff, choosing an appropriate commit type and scope across backend, frontend, docs, and infra-related changes.
  • Pre-push safety validations: Runs targeted checks for syntax issues, forgotten debug code, TODO markers, multi-tenant query safety (e.g., missing liga_id), basic route protection signals, and potential secret exposure.
  • Automated push + main merge + deploy awareness: Pushes the current branch, then merges feature branches into main so GitHub Actions can trigger the Docker-based deployment; supports full sync verification across all environments.

Quick Start

Tell the assistant: “faça um git push” (or “sync total” if you also want end-to-end verification of local = remote = VPS Docker).

Frequently Asked Questions about Git-Commit-Push

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

FAQPage Schema
How do I verify my local repo, GitHub main, and VPS Docker deployment are on the same commit?▼

Verifying local, GitHub main, and VPS Docker deployment sync involves running a full sync verification that checks commit parity and runtime health via GitHub Actions and VPS health endpoints.

How do I enforce conventional commit messages when pushing code changes?▼

Enforcing conventional commit messages when pushing is handled by structuring commits automatically from the detected diff, choosing an appropriate type and scope across backend, frontend, docs, and infra changes.

What pre-push validations should I run to prevent broken Docker deployments?▼

Pre-push validations to prevent broken Docker deployments include targeted checks for syntax issues, forgotten debug code, TODO markers, multi-tenant query safety like missing liga_id, route protection signals, and secret exposure.

Does this workflow support pushing feature branches and merging into main for GitHub Actions?▼

Yes, this workflow supports pushing feature branches and automatically merges them into main so GitHub Actions can trigger the Docker-based deployment to the VPS.

When should I use a verify-only check instead of a full git push and deploy?▼

A verify-only check is suitable when you need to confirm environment parity and runtime health across local, GitHub, and VPS Docker without committing new changes or triggering a deployment.