commit

Enforce Conventional Commits, branch naming, and PR guidelines for Git workflows.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/BobJu0721/line-bot --skill commit-bobju0721
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/BobJu0721/line-bot/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/BobJu0721/line-bot --skill commit-bobju0721

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and enforces a cohesive Git workflow for AI agents by standardizing commit messages, branch naming, and PR processes to ensure a clear, auditable history and collaborative efficiency.

Core Features & Use Cases

  • Enforces Conventional Commits with standardized types and subject lines.
  • Provides branch naming conventions and PR guidelines to streamline reviews.
  • Includes a comprehensive pre-commit checklist to prevent common mistakes and ensure quality.

Quick Start

Start by applying Conventional Commits and the defined branch guidelines to your project and try a sample commit like feat(auth): add OAuth2 login.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce a conventional commits workflow for AI agents?

Conventional commits standardize commit messages using defined types and subject lines to ensure a clear, auditable Git history. This workflow enforces structured messaging and branch naming conventions for collaborative development.

What is the best way to structure Git pull request guidelines for consistent reviews?

The best way to structure Git pull request guidelines is to combine standardized branch naming conventions with a comprehensive pre-commit checklist. This prevents common mistakes and streamlines the review process for structured workflows.

Can I use predefined commit types like feat for my Git branching strategy?

Yes, you can use predefined commit types like feat for your Git branching strategy. The workflow defines specific commit types and subject lines, such as feat(auth): add OAuth2 login, to standardize messaging across typical scenarios.

Does a pre-commit checklist help prevent common mistakes in a Git workflow?

A pre-commit checklist helps prevent common mistakes in a Git workflow by providing documented guidelines and guardrails before submission. It ensures quality control and adherence to standardized commit and PR processes.

Why does standardizing branch naming improve AI agent development workflows?

Standardizing branch naming improves AI agent development workflows by creating a clear, auditable history and streamlining collaborative code reviews. It provides structured guidelines that prevent disorganized repository states across typical scenarios.