skills.rest
highflame-ai
highflame-aiOFFICIAL
Explore all skills by this author →
Website𝕏@javelinaiGitHub

git-workflow

Validate git commit messages and branch names against CI regex patterns.

4|Updated Jul 20, 2026
Search Tags:#automation#git#workflow#ci#atomic-commits#pull-request
One-click install
npx skills add https://github.com/highflame-ai/ai-factory --skill git-workflow-highflame-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/git-workflow
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill git-workflow-highflame-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates friction between local development and CI/CD pipelines by enforcing standardized commit subjects, atomic commit practices, and structured branch naming conventions.

Core Features & Use Cases

  • Automated Validation: Uses local hooks to verify commit prefixes against CI-defined regex patterns before you push.
  • Workflow Orchestration: Provides standardized patterns for branching, worktree usage, and PR creation to ensure clean, reviewable code.
  • Use Case: When you are about to commit a feature, this skill ensures your commit message follows the Conventional Commits standard or your organization's specific regex, preventing unnecessary CI failures and ensuring a clean, revertible git history.

Quick Start

Use the git-workflow skill to validate your current branch naming and commit subject against the repository configuration.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce atomic git commits before pushing to CI?▼

Git commit message standardization applies regex-based validation to enforce Conventional Commits prefixes locally. It prevents CI/CD pipeline failures by verifying commit subjects against organizational patterns before submission.

How do I standardize branch naming conventions for pull requests?▼

Standardized branch naming conventions apply structured workflow patterns to match CI gatekeeper requirements. This ensures consistent PR creation and facilitates clean, reviewable code and multi-PR feature coordination.

Does this git workflow automation support worktree management?▼

Yes, this git workflow automation supports worktree management by providing standardized patterns for worktree usage. It orchestrates pre-merge workflows to ensure isolated development environments remain compatible with CI/CD pipelines.

Why do my pull requests fail CI gatekeeper checks?▼

Pull requests fail CI gatekeeper checks when commit messages and branch names do not match configured regex patterns. Applying local validation rules for atomic commits and PR body templates prevents these unnecessary pipeline failures.

What is the best way to coordinate multiple PRs for a single feature?▼

Coordinating multiple PRs for a single feature requires automated pre-merge orchestration. This manages branch dependencies, ensuring atomic commits merge in sequence to maintain a clean, revertible git history.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
levkisslevkiss

github

Manage GitHub repositories via GitHub CLI for commits, branches, pull requests, issues, releases, and Pages deployment.

Community
Advanced
caseymanoscaseymanos

git-hooks

Configure Husky Git hooks for pre-commit linting, pre-push testing, and commit message validation.

Community
Advanced
ysoftmanysoftman
9

commit

Review changes, lint/format files, and create an English commit message.

Community
Intermediate