git-workflow

Automate Git workflow governance with commitlint and trunk-based development.

2|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/aboudou-cto-bloko/pixelmart --skill git-workflow-aboudou-cto-bloko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/aboudou-cto-bloko/pixelmart/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/aboudou-cto-bloko/pixelmart --skill git-workflow-aboudou-cto-bloko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow governance for Pixel-Mart ensures consistent commits, branch strategies, and PR/CI/CD processes, reducing integration issues and deployment risks.

Core Features & Use Cases

  • Enforces trunk-based development with guarded mainline and feature branches (feat/, fix/, hotfix/, schema/, ui/, refactor/).
  • Standardizes commit messages via commitlint to maintain readable history and reliable changelogs.
  • Manages PR workflows and CI checks to ensure code quality before merging into main.
  • Provides guardrails to block direct pushes to main and require squash merges for clean history.

Quick Start

Start by configuring your repository to enforce trunk-based development and conventional commits using commitlint, then create a feature branch and open a PR for CI validation.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce conventional commits and block direct pushes to main?

To enforce conventional commits and block direct pushes to main, you need Git workflow governance that uses commitlint for message standardization and branch protection rules to guard the mainline, ensuring all changes require a pull request.

What is trunk-based development and how do feature branches work with it?

Trunk-based development is a Git workflow strategy with a guarded mainline where developers create short-lived feature branches. This governance standardizes prefixes like feat/, fix/, hotfix/, schema/, ui/, and refactor/ before merging via pull requests.

How do I set up CI checks and PR reviews for feature branches?

You can set up CI checks and PR reviews by configuring your repository to require validation before merging into main. This workflow governance manages the pull request process to ensure code quality and CI validation pass for feature branches.

Does commitlint work with squash merges to maintain a clean Git history?

Yes, commitlint works with squash merges to maintain a clean Git history. The workflow governance requires squash merges for conventional commit validation, ensuring readable history and reliable changelogs while enforcing valid PR titles.

What are the limitations of enforcing branch naming conventions in Git?

A limitation of enforcing branch naming conventions is that developers must strictly use allowed prefixes like feat/, fix/, or refactor/ for trunk-based development. Deviating from these schema patterns will block PR creation and CI validation processes.

Do I need a specific CI/CD platform to automate pull request workflows?

You do not need a specific CI/CD platform to automate pull request workflows. The governance applies standard Git mechanisms for PR creation, valid PR titles, and CI checks, making it compatible with any platform supporting branch protection.