git-workflow

Configures GitHub Actions workflows for trunk-based development and semantic versioning.

Updated Dec 13, 2025

Search Tags:#git #devops #ci/cd #release #semantic-versioning #conventional-commits

Ready to run

npx skills add https://github.com/imehr/vet --skill git-workflow-imehr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/imehr/vet/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/imehr/vet --skill git-workflow-imehr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured DevOps and Release Engineering guidance to standardize workflows, improve release predictability, and reduce manual toil by enforcing trunk-based development, conventional commits, and automated pipelines across modern CI/CD toolchains.

Core Features & Use Cases

Enforces Conventional Commits and semantic versioning to create reliable release histories.
Guides CI/CD architecture, PR templates, and automated release processes with standard tooling.
Use Case: Configure a GitHub Actions workflow that runs on PRs, publishes a semantic release, and updates CHANGELOG.md.

Quick Start

Ask the AI to configure your repository for trunk-based development with conventional commits and semantic versioning, and to set up automated releases using GitHub Actions.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I set up automated semantic versioning and releases with GitHub Actions?▼

Automated semantic versioning and releases with GitHub Actions are achieved by enforcing conventional commits and trunk-based development to trigger pipeline-driven version bumps and CHANGELOG.md updates. This approach standardizes release predictability and reduces manual toil.

What is trunk-based development and how does it improve CI/CD workflows?▼

Trunk-based development is a DevOps strategy where developers merge small, frequent updates into a main branch, improving CI/CD workflows by enabling continuous automated testing and reducing complex merge conflicts. It ensures reliable release histories when paired with conventional commits.

Do I need conventional commits to automate semantic versioning in my pipeline?▼

Yes, conventional commits are required to automate semantic versioning in your pipeline because they provide the structured commit messages necessary to programmatically determine version bumps. This standardizes your release engineering and creates reliable release histories.

What's the best way to enforce DevOps governance for pull requests?▼

The best way to enforce DevOps governance for pull requests is by applying standardized PR templates alongside automated CI/CD pipelines that validate conventional commits before merging. This ensures consistent release engineering and reduces manual toil across modern toolchains.

Can I use this release engineering strategy with CI/CD tools other than GitHub Actions?▼

Yes, this release engineering strategy targets automated pipelines across modern CI/CD toolchains similar to GitHub Actions. It provides structured DevOps guidance to standardize workflows, enforce semantic versioning, and improve release predictability across compatible platforms.