git

Automate Git staging, conventional commits, secret scans, and pull requests.

Updated Feb 27, 2026

Search Tags:#automation #git #workflow #security #commit #branching #pr

Ready to run

npx skills add https://github.com/haidonglethqb/CloudSchool --skill git-haidonglethqb

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates Git workflows with conventional commits to enforce standards and detect secrets before commits.

Core Features & Use Cases

Conventional-commit enforcement: ensures commits follow the type/scope guidance and auto-splits commits when needed.
Security scans before commit: blocks risky changes by detecting common secrets.
PR and merge automation: coordinates PR creation and merges via a git-manager subagent for clean, auditable history.
Workflow orchestration: supports standard commands like cm (stage + commit), cp (stage + commit + push), pr (pull request), and merge.

Quick Start

Staging all changes, commit with a conventional message, push to the remote, and open a pull request.

Frequently Asked Questions about git

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

FAQPage Schema

How do I automate git commits with conventional commit standards?▼

Automate git commits by enforcing a front-end rule set that validates conventional commit types and scopes, automatically splitting changes into separate commits when needed to maintain strict history standards.

How can I prevent committing secrets into my git repository?▼

Prevent committing secrets by running automated pre-commit security scans that detect common risky patterns and block the commit operation before any sensitive data reaches the remote repository history.

What is the best way to automate pull requests and merges for feature branches?▼

Automate pull requests and merges for feature branches by using dedicated workflow commands to coordinate PR creation and merge operations, ensuring a clean, auditable Git history across standard development scenarios.

Can I stage, commit, and push git changes in a single automated workflow?▼

Stage, commit, and push git changes in a single workflow by using the cp command, which orchestrates the entire sequence while applying conventional commit rules and security scans automatically.

Does this git workflow automation require specific branching or pull request tools?▼

Git workflow automation requires no external branching or pull request tools, operating directly via built-in commands like cm, cp, pr, and merge to manage standard Git operations and feature branch lifecycles.

Why should I use automated conventional commits instead of manual git commits?▼

Use automated conventional commits to enforce consistent type and scope rules across development teams, auto-split changes by category, and prevent secret leaks before pushing, which manual commits lack the tooling to validate.