git

Automate safe Git workflows with conventional commits and coordination rules.

Updated Jun 30, 2026

Search Tags:#git #collaboration #branch-management #version-control #conventional-commits #workflow-safety

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow and safety rules for this workspace help teams coordinate changes, avoid destructive actions, and maintain clean history.

Core Features & Use Cases

Policy-driven workflows: Enforce status checks before commits, require coordination before removing others' changes, and promote atomic commits with conventional messages.
Safe collaboration: Guide branch management, rebases with explicit approvals, and non-destructive edits.
Use Case: Imagine you need to revert a feature while preserving teammates' work; this skill advises on safe reverts, coordination, and messaging.

Quick Start

Check status, review diffs, and commit with a conventional message following the safety rules. Then push after coordinating with your team.

Frequently Asked Questions about git

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

FAQPage Schema

How do I enforce conventional commits and safe Git workflows across a team workspace?▼

Safe Git workflows are enforced by applying policy rules that require status checks before commits, mandate conventional commit messages, and prohibit destructive commands without explicit approval.

What's the best way to coordinate Git branch management and prevent losing teammates' changes during a rebase?▼

Git branch management and rebases require explicit coordination before removing others' changes, ensuring non-destructive edits and safe collaboration across the workspace.

How do I safely revert a Git feature without overwriting my team's recent commits?▼

To safely revert a Git feature, the workflow advises on safe reverts, requires coordination with teammates, and enforces messaging rules to preserve existing work.

Can I execute Git squash and conflict resolution operations without risking destructive side effects?▼

Executing Git squash and conflict resolution safely requires checking status before commits and obtaining explicit approvals for any potentially destructive commands.

Does this Git workflow safety approach apply to atomic commits and local version control?▼

The Git workflow safety approach applies to local version control by promoting atomic commits with conventional messages and enforcing safety rules before any changes are pushed.