skills.rest
Conceptual-Machines
Conceptual-MachinesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git

Enforce Git workflow rules for branching, committing, and pull requests.

195|21|Updated Jan 17, 2026
Search Tags:#git#workflow#branching#commits#code-review#pull-requests
One-click install
npx skills add https://github.com/Conceptual-Machines/magda-core --skill git-conceptual-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/Conceptual-Machines/magda-core/tree/main/.claude/skills/git
Command: npx skills add https://github.com/Conceptual-Machines/magda-core --skill git-conceptual-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow rules ensure consistent branching, committing, and pushing to prevent risky operations and maintain a clean repository history.

Core Features & Use Cases

  • Enforce branch naming conventions and a PR-based workflow
  • Prevent pushes to main or other protected branches without review
  • Define when to use resets, rebases, or force pushes with explicit user confirmation

Quick Start

Follow these Git workflow rules for all feature development, branching, and pushing.

Frequently Asked Questions about git

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

FAQPage Schema
How do I prevent pushing directly to the main branch in a git workflow?▼

Git workflow rules prevent pushes to main by enforcing a pull request-based review process. You must create a separate branch for features or fixes and submit a pull request for merging to maintain a clean repository history.

What is the best way to name branches for feature development and fixes?▼

Branch naming conventions standardize feature development and bug fixes in a git workflow. Following consistent naming patterns across branches ensures organized tracking and prevents unsafe operations when committing changes and submitting pull requests.

When should I use force push or resets in my repository?▼

Use force pushes and resets only with explicit user confirmation during complex history modifications. Git workflow rules constrain these operations to prevent risky actions and ensure a clean repository history is maintained across development tasks.

Can I use this git workflow for both feature additions and bug fixes?▼

Yes, this git workflow applies to daily development tasks including both feature additions and bug fixes. It organizes branching, committing changes, and submitting pull requests consistently across all development activities to ensure safe collaboration.

How do I enforce code review rules before merging pull requests?▼

Enforcing code review rules requires a git workflow that prevents direct pushes to protected branches. By mandating pull requests for all merges, the workflow ensures changes are reviewed before integration into the main repository history.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
samChang72samChang72
1

code-review

Automates code reviews to detect bugs, style violations, and performance issues in submissions via static analysis tools.

Community
Intermediate
jg-chalk-iojg-chalk-io

moai-foundation-git

Implement production-grade Git workflows with branching strategies and Conventional Commits.

Community
Advanced