git-best-practices

Standardizes Git branching, commits, and Husky pre-commit checks for teams.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/curiositech/port-daddy --skill git-best-practices-curiositech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-best-practices
Source: https://github.com/curiositech/port-daddy/tree/main/skills/git-best-practices
Command: npx skills add https://github.com/curiositech/port-daddy --skill git-best-practices-curiositech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows often become chaotic in teams without a shared set of conventions. This skill provides standardized branching strategies, commit conventions, and tooling practices to keep histories readable and merges predictable.

Core Features & Use Cases

  • Branching Strategy: guidelines for trunk-based development and feature branches to balance speed and stability.
  • Commit Conventions & Hooks: guidance on conventional commits, commit messages, and using Husky + lint-staged to enforce quality.
  • Monorepo & Worktrees: patterns for managing multi-package repos and parallel AI agent worktrees with minimal conflicts.
  • Use Case: a mid-sized project with multiple teams can align on a single workflow to reduce merge conflicts and improve release reliability.

Quick Start

Configure your repo to adopt trunk-based development, set up conventional-commit messages, and enable pre-commit checks with Husky.

Frequently Asked Questions about git-best-practices

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

FAQPage Schema
How do I standardize Git workflows to prevent chaotic histories and inconsistent merges?

Standardize Git workflows by adopting trunk-based development, enforcing conventional commit messages, and enabling pre-commit checks with Husky and lint-staged to keep histories readable and merges predictable.

What is the best way to manage Git branches in a monorepo with multiple teams?

Managing Git branches in a monorepo is best achieved through trunk-based development and feature branches, balancing deployment speed and stability while reducing merge conflicts across multiple teams.

How do I set up conventional commits with Husky and lint-staged for pre-commit checks?

Set up conventional commits by configuring Husky to run lint-staged as a pre-commit hook, enforcing commit message conventions and code quality automatically before changes are merged.

Can I use feature branches and trunk-based development together for multi-repo projects?

Feature branches and trunk-based development can be used together for multi-repo projects, providing guidelines that coordinate code reviews and maintain release reliability across repositories.

How do Git worktrees handle parallel AI agent workflows in a monorepo?

Git worktrees manage parallel AI agent workflows in a monorepo by enabling isolated working directories, minimizing conflicts and streamlining multi-package development across branches.

Why should I use conventional commits for team Git workflows?

Conventional commits should be used for team Git workflows to standardize commit messages, prevent chaotic histories, and ensure merges remain predictable during coordinated code reviews.