git-workflow

Manage Git branches, atomic commits, and pull request preparation.

Updated Dec 25, 2025

Search Tags:#git #workflow #code review #pull request #commit #branching

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines Git operations, ensuring consistent and safe code management practices throughout the development lifecycle.

Core Features & Use Cases

Branching Strategies: Guides users on creating and managing feature, fix, and experiment branches.
Atomic Commits: Enforces small, self-contained commits for better traceability and easier rollbacks.
Pre-Commit Verification: Outlines necessary checks before committing code, tailored to risk levels.
Pull Request Preparation: Details steps for code review and final verification before merging.
Use Case: When starting a new feature, this skill helps you create the correct branch, commit your work following best practices, and prepare for a smooth pull request.

Quick Start

Use the git-workflow skill to create a new feature branch named 'feature/user-authentication'.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I enforce atomic commits and conventional commit messages in my Git workflow?▼

To enforce atomic commits, this Git workflow Skill guides you in creating small, self-contained commits and mandates conventional commit messages, resulting in improved code traceability and easier rollbacks.

What is a risk-based branching strategy for managing feature and fix branches?▼

A risk-based branching strategy evaluates code impact to guide the creation and management of feature, fix, and experiment branches, ensuring appropriate pre-commit verification checks are applied before integration.

How do I prepare a pull request for code review and final verification?▼

Preparing a pull request involves detailing necessary code review steps and final verification checks before merging, ensuring your feature branch meets maintainability and safety standards for integration.

Can I get proactive commit suggestions and branch cleanup post-merge?▼

Yes, this Git workflow supports proactive commit suggestions during development and automates branch cleanup post-merge to maintain a clean and efficient repository state throughout the lifecycle.

What's the best way to structure a Git workflow for new feature development?▼

The best way to structure a Git workflow for new features is using risk-based branching to create a specific feature branch, followed by atomic commits and structured pull request preparation for smooth integration.