git-workflow

Enforce conventional commit format and structured PR workflows across git repositories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aldengolab/lorist --skill git-workflow-aldengolab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/aldengolab/lorist/tree/main/skills/git-workflow
Command: npx skills add https://github.com/aldengolab/lorist --skill git-workflow-aldengolab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardizes and enforces consistent git commit messages and PR workflows to reduce confusion and review overhead across repositories.

Core Features & Use Cases

  • Enforces conventional commit format across commits and PRs
  • Breaking Change Detection and automatic validations
  • Updates docs and Makefiles as part of PR workflows
  • Generates structured PR descriptions with honest test plans
  • Verifies PR title/body coherence and branch-PR consistency
  • Pairs with lorist-git MCP server for deterministic tool execution

Quick Start

Apply the git-workflow rules to every commit and PR to maintain consistency across the project.

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 commit format across all my git repositories?

Conventional commit enforcement applies standardized rules during commits and PR creation, ensuring commit messages follow consistent formatting and breaking changes are automatically detected across all git repositories.

What is the best way to automate pull request workflow with structured descriptions and test plans?

Automating pull request workflow generates structured PR descriptions with honest test plans, verifies title and body coherence, and ensures branch-PR consistency through deterministic rule enforcement during PR creation.

Can I automatically detect breaking changes in my commit messages and pull requests?

Breaking change detection runs automatically during commit and PR validation, flagging changes that require documentation and Makefile updates as part of the enforced PR workflow.

Do I need a specific MCP server to execute deterministic git workflow tool calls?

The git workflow pairs with the lorist-git MCP server to execute deterministic tool calls, ensuring automated commit formatting, PR description generation, and branch handling produce consistent, repeatable results.

Why does my pull request workflow require documentation and Makefile updates?

Documentation and Makefile updates are enforced as part of the comprehensive PR workflow to ensure build configurations and project docs remain coherent and accurately reflect submitted code changes.

What are the limitations of automating conventional commit and PR workflow enforcement?

Enforcement requires consistent application across all repositories and pairing with the lorist-git MCP server for deterministic execution; repositories with pre-existing non-conventional commit histories may require migration effort.