git

Standardize Git workflows with Conventional Commits, Lefthook hooks, and PR templates.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/leovido/leo-skills --skill git-leovido
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/leovido/leo-skills/tree/main/skills/git
Command: npx skills add https://github.com/leovido/leo-skills --skill git-leovido

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow standards, commit conventions, hooks, and pull request practices. Use this when users need guidance on Conventional Commits, Git hooks with Lefthook, pull request templates, .gitignore configuration, or Git workflow best practices for team collaboration.

Core Features & Use Cases

  • Conventional Commits: Enforce a standard commit message format across the team.
  • Hook & Template Guidance: Provide standardized Lefthook configuration and PR templates to automate checks and consistency.
  • Ignore & Best Practices: Recommend .gitignore patterns and collaboration practices to streamline teamwork across repositories.

Quick Start

Use this skill to align your team's Git practices for a new project.

Frequently Asked Questions about git

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

FAQPage Schema
How do I enforce conventional commits across my team's git workflow?

Standardizing pull request templates streamlines teamwork by documenting explicit review criteria and checklist patterns. Using PR templates enforces correct git usage and consistency across multiple repositories, ensuring all necessary context is provided before merging code changes.

How do I configure Lefthook for git hooks automation?

Configuring Lefthook for git hooks involves defining explicit configuration examples that automate checks like linting and testing. Lefthook integration standardizes local git hooks across a team, enforcing correct git usage before code is committed or pushed to remote repositories.

What are the best .gitignore patterns for collaborative software projects?

The best .gitignore patterns for collaborative projects recommend standard rules to exclude build artifacts, dependencies, and environment files. Proper .gitignore configuration prevents sensitive data leaks and repository bloat, streamlining teamwork across multiple repositories with consistent ignore practices.

When do I need to standardize git workflow practices for my repositories?

You need to standardize git workflow practices when aligning collaborative software projects requiring consistent conventions. Adopting standardized commit conventions, hooks, and pull request practices is essential for team collaboration to avoid integration conflicts and maintain repository health across multiple projects.