commit

Create conventional commits and sync beads issue tracking with git.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/claude --skill commit-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jfmyers9/claude/tree/main/skills/commit
Command: npx skills add https://github.com/jfmyers9/claude --skill commit-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creating conventional commits and syncing beads-based issue tracking with the commit workflow.

Core Features & Use Cases

  • Parse commit messages to enforce conventional formats, and support --amend and --fixup.
  • Inspect git status and staged changes, ensuring meaningful commits or prompting for action.
  • Execute commits with the appropriate git commands (normal, amend, fixup) and format multi-line bodies as needed.
  • Sync beads state automatically after commits using the bd CLI to keep issue tracking up to date.

Quick Start

Create a conventional commit with the provided message, optionally using --amend or --fixup, then run beads synchronization.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commits and sync issue tracking?

You can automate conventional commits and sync issue tracking by parsing commit messages, validating formats, executing git commands, and running beads synchronization to keep issue states updated.

Does this workflow support git amend and fixup flags?

Yes, the workflow supports git amend and fixup flags by parsing them directly, validating the commit message, and executing the appropriate git command while maintaining beads sync.

What is beads sync in a version-control workflow?

Beads sync in a version-control workflow automatically updates issue tracking states using the bd CLI immediately after a commit is executed, ensuring development progress stays aligned.

How do I enforce conventional commit formats before executing git commands?

To enforce conventional commit formats, the workflow inspects staged changes, parses the provided message against conventional standards, and prompts for action if the validation fails before executing.

Can I format multi-line commit bodies with this automation tool?

Yes, you can format multi-line commit bodies with this automation tool, as it parses the message, applies conventional formatting rules, and structures the body before executing the git commit.