skills.rest
jralph
jralphCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Enforce Conventional Commits, pre-commit hooks, and semantic versioning in Git workflows.

Updated Feb 1, 2026
Search Tags:#git#workflow#branching#pre-commit#release-management#pull-request#conventional-commits
One-click install
npx skills add https://github.com/jralph/.config-opencode --skill git-workflow-jralph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/jralph/.config-opencode/tree/main/skills/git-workflow
Command: npx skills add https://github.com/jralph/.config-opencode --skill git-workflow-jralph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Git workflows, commit conventions, and release processes to reduce mistakes, improve collaboration, and accelerate delivery across teams.

Core Features & Use Cases

  • Commit message conventions aligned with Conventional Commits v1.0.0 to ensure clear history and automated changelog generation.
  • Pre-commit hooks to enforce formatting, secret detection, and linting before changes are committed.
  • Pull Request standards and templates to streamline code reviews and ensure consistency.
  • Branching strategy guidance with descriptive, ticket-referenced naming conventions for predictable workflows.
  • Release management practices including semantic versioning, changelog maintenance, and automated gating through CI/CD.
  • Use Case: A team adopts this Skill to enforce a unified git workflow across feature, bugfix, and release branches, reducing review time and integration issues.

Quick Start

Configure your repository to use Conventional Commits, enable pre-commit checks, and align PR templates and branch names to the Skill's guidelines.

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 in my Git workflow?▼

You can enforce Conventional Commits by standardizing your Git workflow with pre-commit checks and pull request templates that validate commit message formats. This ensures a clear history and automates changelog generation across feature and bugfix branches.

What is the best way to standardize branch naming for pull requests?▼

The best way to standardize branch naming is to adopt a descriptive, ticket-referenced naming convention across feature, fix, and hotfix branches. This predictable workflow streamlines code reviews and reduces integration issues during release management.

How do pre-commit hooks improve release management?▼

Pre-commit hooks improve release management by enforcing formatting, secret detection, and linting before changes are committed. This reduces mistakes and accelerates delivery across teams by preventing invalid code from entering your branches.

Can I use semantic versioning with automated CI/CD gating?▼

Yes, you can use semantic versioning with automated CI/CD gating to manage releases. This Skill aligns release management practices including semantic versioning, changelog maintenance, and automated gating to standardize your delivery pipeline.

Does this Git workflow approach require specific dependencies to function?▼

No, this Git workflow approach does not require specific external dependencies to function. It provides guidelines for Conventional Commits v1.0.0, pre-commit hooks, PR standards, branch naming, and semantic versioning without third-party tool restrictions.

Related Skills

Explore More Software Engineering Skills→
jralphjralph

git-workflow

Enforce Conventional Commits, pre-commit hooks, and semantic versioning in Git workflows.

Community
Intermediate
avav25avav25
2

release

Automate version bumps, changelog generation, git tagging, and release notes.

Community
Advanced
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate
rnavarychrnavarych
14

git-workflows

Guide Git branching, commit conventions, and pull request workflows.

Community
Intermediate