git-workflow

Validate Git commit messages, staging practices, and push commands.

Updated Mar 31, 2026

Search Tags:#git #workflow #commit #push #pre-commit #branch

Ready to run

npx skills add https://github.com/shellicar/skills --skill git-workflow-shellicar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/shellicar/skills/tree/main/skills/git-workflow
Command: npx skills add https://github.com/shellicar/skills --skill git-workflow-shellicar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Git commit messages, improper staging, and incorrect push commands lead to messy history and deployment issues. This Skill provides clear conventions to keep Git history clean and collaborative.

Core Features & Use Cases

Commit Message Rules: Enforce concise, imperative, under‑50‑character messages without prefixes.
Staging Guidelines: Require explicit file paths and run pre‑commit checks before committing.
Push Procedures: Specify correct commands for new and existing branches and handle pre‑commit hook failures.
Convention Detection: Run scripts to identify repository conventions and apply appropriate naming rules.

Quick Start

Use the git-workflow skill to validate my commit message and get the correct push command.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I enforce consistent git commit messages in my repository?▼

To enforce consistent git commit messages, this Skill validates that messages are concise, use imperative mood, and stay under 50 characters without prefixes. It checks these rules during staging and pre-push phases to keep your Git history clean and collaborative.

What is the correct way to stage files and run pre-commit checks in Git?▼

The correct way to stage files is by specifying explicit file paths rather than using bulk adds. This Skill requires running pre-commit checks on those explicitly staged files before finalizing the commit to ensure code quality.

How do I get the correct git push command for new and existing branches?▼

To get the correct git push command for new and existing branches, this Skill specifies the exact push commands needed. It also handles pre-commit hook failures to prevent unsafe flags from disrupting your deployment workflow.

How can I detect and apply Git branch naming conventions automatically?▼

To detect and apply Git branch naming conventions, this Skill runs scripts that identify existing repository conventions. It automatically applies the appropriate naming rules during your code review and pre-push phases.

Why should I avoid bulk adds and unsafe flags when committing code?▼

You should avoid bulk adds and unsafe flags because they lead to improper staging and messy history. This Skill enforces explicit file paths and safe push commands to prevent incorrect commands from causing deployment issues.