production-git

Enforce git workflow practices for branching, commits, PRs, and releases.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/nkartik94/agentic-skills --skill production-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-git
Source: https://github.com/nkartik94/agentic-skills/tree/main/skills/production-git
Command: npx skills add https://github.com/nkartik94/agentic-skills --skill production-git

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git workflows often become inconsistent, leading to merge conflicts, accidental deployments, and confusing history. This skill provides a standardized framework for branching, committing, reviewing, releasing, and rolling back production-ready code.

Core Features & Use Cases

  • Branch naming conventions (feat/, fix/, hotfix/, refactor/) to keep history readable and predictable.
  • Commit messaging with Conventional Commits to automate changelogs and releases.
  • PR workflow guidance and release management to coordinate reviews and deployments.
  • Hotfix and rollback procedures to quickly stabilize production.
  • Version tagging with semantic versioning to track releases consistently.

Quick Start

Create a feature branch (feat/description), commit with Conventional Commits, and open a PR against main to begin implementing changes.

Frequently Asked Questions about production-git

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

FAQPage Schema
How do I standardize git workflow branching to prevent deployment issues?

Standardize git workflow branching by enforcing branch prefixes like feat/, fix/, and hotfix/ to keep history readable and prevent accidental deployments. This ensures predictable release management and coordinated pull requests across main and release branches.

What is the best way to enforce Conventional Commits for automated changelogs?

Enforce Conventional Commits by applying standardized commit messaging rules during pull request reviews. This structures commit history to automate changelog generation and track semantic versioning consistently across release branches.

How do I create a hotfix and rollback procedure for production git branches?

Create a hotfix and rollback procedure by using the hotfix/ branch prefix to quickly stabilize production. The workflow supports tagging releases with semantic versioning and running deployment checks to validate rollback procedures on main and release branches.

When do I need semantic version tagging in a git release workflow?

You need semantic version tagging in a git release workflow to track releases consistently and coordinate deployments. Version tagging works alongside Conventional Commits to automate changelogs and ensure stable rollback procedures for production-ready code.

Can I use this git workflow framework without any external dependencies?

Yes, you can use this git workflow framework without external dependencies. It operates as a standalone reference component that standardizes branch naming, commit messaging, PR reviews, and release tagging across your repository.

Why does inconsistent git branching cause merge conflicts and deployment issues?

Inconsistent git branching causes merge conflicts and deployment issues because unpredictable history and unstructured commit messages prevent automated changelog generation and complicate release management coordination across main and release branches.