skills.rest
adelpro
adelproCOMMUNITY
Explore all skills by this author →
Website𝕏@adelproGitHub

git-workflow

Enforce conventional commits, branch naming, PR etiquette, and release tagging.

2|Updated Mar 21, 2026
Search Tags:#git#workflow#code-review#pull-request#conventional-commits#branch-naming#release-tagging
One-click install
npx skills add https://github.com/adelpro/openclaw-arsenals --skill git-workflow-adelpro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/adelpro/openclaw-arsenals/tree/main/02-skills/git-workflow
Command: npx skills add https://github.com/adelpro/openclaw-arsenals --skill git-workflow-adelpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce clean Git workflow across projects by standardising commits, branch naming, PR etiquette, and release tagging, reducing messy histories and review friction.

Core Features & Use Cases

  • Conventional commits: Enforce standardized commit messages to improve history clarity.
  • Branch naming: Enforce consistent naming conventions for features, fixes, and chores.
  • PR etiquette: Regularize review processes, approvals, and merge strategies to improve quality.
  • Release tagging: Standardize semantic version tagging and changelog generation to streamline releases.

Quick Start

Install and configure this skill in your repository to enforce conventional commits, branch naming, PR etiquette, and release tagging from day one.

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 across my team's Git workflow?▼

This skill automates conventional commit enforcement across Git workflow by standardizing commit messages, improving history clarity and reducing review friction during feature development.

What's the best way to standardize branch naming conventions for features and fixes?▼

The optimal approach is enforcing consistent branch naming rules for features, fixes, and chores within Git workflow, which regularizes governance and maintains reproducible project history.

Can I automate pull-request etiquette and review processes for solo development?▼

Yes, PR etiquette and review processes can be automated for solo development workflows, applying configurable guards and merge strategies to maintain consistent quality standards.

Does this Git workflow skill support automatic semantic version tagging for releases?▼

Yes, it supports automatic semantic version tagging for releases by standardizing release tagging and generating changelogs, ensuring reproducible delivery across integration pipelines.

How do I configure guards and error handling for a clean Git workflow?▼

You configure guards and error handling during repository setup, applying customizable rules to commits, branches, and PRs to prevent messy histories and enforce governance.

Related Skills

Explore More Software Engineering Skills→
yuridefrancayuridefranca

github-pr-creator

Create GitHub pull requests with project-specific base-branch rules and templates.

Community
Advanced
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
nq-rdlnq-rdl

pre-commit

Manage multi-language pre-commit hooks from .pre-commit-config.yaml using pixi.

Official
Intermediate