skills.rest
ebongard
ebongardCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Enforce Git workflow rules for commits, pushes, branches, and pull requests.

34|5|Updated Jan 15, 2026
Search Tags:#git#workflow#documentation#pull-request#commit-message#branch-protection#issue-number
One-click install
npx skills add https://github.com/ebongard/renfield --skill git-workflow-ebongard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ebongard/renfield/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/ebongard/renfield --skill git-workflow-ebongard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces repository Git policies to prevent accidental pushes, ensure every commit is linked to an issue, maintain up-to-date documentation, and standardize commit and PR messages for Renfield development workflows.

Core Features & Use Cases

  • Commit Standards: Ensures every commit follows the prescribed type(scope): message format, includes an issue number, and contains a Co-Authored-By line.
  • Push Safety & Branching: Prevents direct pushes to main, enforces feature-branch workflows, and requires explicit confirmation before any git push.
  • PR & Documentation Workflow: Requires documentation updates before push and generates structured PR titles and bodies for consistent reviews and traceability.

Quick Start

Prepare a properly formatted commit message, ask for the issue number, ensure documentation sections are updated, include the Co-Authored-By line, and draft a PR title and body ready for creation.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce a consistent git commit message format across a development team?▼

To enforce a consistent git commit message format, this Skill requires commits to follow a structured type(scope): message format, include a specific issue number, and append a Co-Authored-By line for traceability. This ensures standardized commit history across team repositories.

How do I prevent accidental pushes to the main branch?▼

To prevent accidental pushes to the main branch, this Skill enforces branch protection by blocking direct pushes and requiring a feature-branch workflow. It also mandates explicit user confirmation before executing any git push command.

How do I link documentation updates to pull request creation?▼

To link documentation updates to pull request creation, this Skill requires documentation sections to be updated before pushing code. It then generates structured PR titles and bodies to ensure consistent reviews and traceability for every pull request.

Does this git workflow enforcement require an issue number for every commit?▼

Yes, this git workflow enforcement requires an issue number for every commit. It prompts users for an issue number during the commit process to ensure all code changes are directly linked to an existing issue for project traceability.

What is the best way to standardize pull request titles and bodies?▼

The best way to standardize pull request titles and bodies is to enforce structured PR message formats during creation. This Skill generates consistent PR titles and bodies, ensuring standardized reviews and clear traceability back to the related issue.

Related Skills

Explore More Software Engineering Skills→
TabooLibTabooLib
388

create-pr

Create a GitHub issue and planning branch from collected feature requirements.

Official
Intermediate
mkikenmkiken
1

pr-create-by-branch

Generate GitHub Pull Request titles and bodies from branch diffs.

Community
Intermediate
PaddlePaddlePaddlePaddle
285

create-pr

Automate git commits, pushes, and pull request creation across multiple repositories.

Official
Intermediate
Minara-AIMinara-AI
28

push

Run pre-flight compile and type checks before pushing git commits.

Official
Advanced