Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/tachfineamnay/LumiraV2 --skill git-workflow-ci-cd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Git Workflow & CI/CD
Source: https://github.com/tachfineamnay/LumiraV2/tree/main/skills/12-git-workflow
Command: npx skills add https://github.com/tachfineamnay/LumiraV2 --skill git-workflow-ci-cd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Git workflows and CI/CD processes across teams, reducing integration frictions, ensuring consistent commit messaging, and automating checks with Husky and GitHub Actions.

Core Features & Use Cases

  • Conventional commits enforcement and commit linting to maintain a clean history.
  • Branching strategies (main, develop, feature/, release/) with guidance for PR workflows.
  • Pre-commit hooks (Husky) to run linting, tests, and formatting before commits.
  • Automated CI/CD pipelines on GitHub Actions for lint, test, build, and deployment.
  • Use Case: Teams adopting a mature release process with automated checks and predictable versioning.

Quick Start

Set up the Git workflow and CI/CD: initialize main and develop branches with feature/, fix/, release/* patterns; enforce conventional commits; install Husky hooks; and enable GitHub Actions for lint, test, build, and deploy.

Frequently Asked Questions about Git Workflow & CI/CD

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

FAQPage Schema
How do I set up a Git workflow with conventional commits and feature branches?

To set up a Git workflow with conventional commits and feature branches, initialize main and develop branches, apply feature/*, fix/*, and release/* patterns, and enforce commit conventions to maintain a clean project history.

How do I automate lint, test, build, and deploy pipelines with GitHub Actions?

Automate lint, test, build, and deploy pipelines using GitHub Actions by configuring CI/CD pipelines that trigger on PR workflows, running automated checks before merging code into the main and develop branches.

How do I enforce commit linting and formatting before commits using Husky?

Enforce commit linting and formatting before commits using Husky by installing pre-commit hooks that execute automated checks, ensuring consistent commit messaging and code formatting prior to integration.

What is the best Git branch strategy for teams adopting a mature release process?

The best Git branch strategy for teams adopting a mature release process uses main, develop, feature/*, fix/*, and release/* branches with predictable versioning, guided by PR workflows to reduce integration frictions.

Do I need GitHub Actions to use Husky pre-commit hooks?

You do not need GitHub Actions to use Husky pre-commit hooks. Husky operates locally to run linting and tests before commits, while GitHub Actions handles remote CI/CD pipelines for build and deployment.

Why use conventional commits in a CI/CD pipeline?

Use conventional commits in a CI/CD pipeline to standardize commit messaging, enable automated versioning, and maintain a clean history, which reduces integration frictions across teams during automated deployments.