commit

Create conventional Git commits and sync them with issue tracking systems.

4|3|Updated Jul 14, 2025

Search Tags:#git #version control #commit #conventional commits #issue tracking #sync

Ready to run

npx skills add https://github.com/luan/dot-claude --skill commit-luan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/luan/dot-claude/tree/main/skills/commit
Command: npx skills add https://github.com/luan/dot-claude --skill commit-luan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of saving code changes by creating well-formatted, conventional commits and synchronizing them with issue tracking systems.

Core Features & Use Cases

Conventional Commits: Enforces a standardized format (type(scope): description) for commit messages, improving readability and automation.
Issue Tracking Sync: Automatically updates issue tracking systems (like Beads) after a successful commit.
Use Case: After completing a feature, use this Skill to generate a feat commit message that includes the relevant issue ID, ensuring your commit history is both informative and linked to your project management.

Quick Start

Use the commit skill to create a conventional commit for your staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I create conventional commits and sync them with issue tracking?▼

To create conventional commits and sync them with issue tracking, you can use this Skill to generate standardized `type(scope): description` messages and automatically update linked issues in Beads after a successful Git commit.

What is the conventional commit format for linking Git history to project management?▼

The conventional commit format for linking Git history to project management is `type(scope): description`, which enforces standardized message readability while embedding the relevant issue ID to synchronize with your issue tracking system.

Do I need Git CLI and Beads CLI to automate conventional commits and issue sync?▼

Yes, you need Git CLI and Beads CLI installed to automate conventional commits and issue sync, as the Skill relies on these command-line interfaces to execute local version control operations and update the remote tracking system.

How do I sync my Git commits with Beads issue tracking after completing a feature?▼

To sync your Git commits with Beads issue tracking after completing a feature, use this Skill to generate a `feat` commit message containing the relevant issue ID, which then automatically updates the linked tracking system upon commit completion.

Can I use this conventional commit tool for software development workflows that do not use Beads?▼

This conventional commit tool is designed for software development workflows requiring version control and integrated task management, but automatic synchronization specifically targets the Beads issue tracking system via the Beads CLI.

Why use conventional commits instead of regular Git commit messages for issue tracking?▼

You use conventional commits instead of regular Git commit messages for issue tracking to enforce a standardized `type(scope): description` format, which improves commit history readability and enables automated synchronization with project management platforms.