skills.rest
cattboy
cattboyCOMMUNITY
Explore all skills by this author →
GitHub

commit

Stage changes and commit with conventional messages enriched by GitHub context.

1|Updated Mar 13, 2026
Search Tags:#automation#git#commit#github#branch-management#conventional-commits
One-click install
npx skills add https://github.com/cattboy/lil_bro --skill commit-cattboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/cattboy/lil_bro/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/cattboy/lil_bro --skill commit-cattboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage all changes and commit with a rich conventional commit message, automatically enriched with GitHub context.

Core Features & Use Cases

  • Auto-enrich commit messages with linked issues and open PRs
  • Detect issue numbers from branch name patterns
  • Retrieve GitHub context via gh
  • Ask clarifying questions only when the diff is ambiguous
  • Trigger on common commit phrases like /commit, "commit my changes", or "make a commit"

Quick Start

Ask me to commit your changes, and I will generate a conventional commit message with GitHub context.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write conventional commit messages with GitHub issue context automatically?▼

To generate a conventional commit message with GitHub context, trigger the workflow with a common phrase like 'commit my changes' or 'make a commit'. The system stages all changes, fetches relevant GitHub data, and only prompts for clarification if the diff is ambiguous.

Can I link open pull requests and issues to my git commit automatically?▼

Yes, you can link open pull requests and issues automatically. By relying on the gh CLI, the workflow detects issue numbers from your branch name and retrieves the corresponding PR details and issues to enrich the commit message.

Does this automated commit workflow require the gh CLI to fetch pull request details?▼

Yes, the workflow relies on the gh CLI to fetch pull request details and linked issues. It parses the branch name for issue numbers and uses gh to retrieve the GitHub context required for the rich commit message.

What is the best way to automate branch management and commit message generation?▼

The best way to automate branch management and commit message generation is to use a workflow that parses branch names for issue numbers and fetches GitHub context automatically. This ensures your commits follow conventional commit standards and reference the correct PRs and issues.

Why does my automated commit workflow prompt for clarification on ambiguous diffs?▼

Your automated commit workflow prompts for clarification on ambiguous diffs to ensure the generated conventional commit message accurately reflects the changes. It only asks clarifying questions when the diff lacks clear context, avoiding unnecessary interruptions.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
mycelium-iomycelium-io
112

ship

Automate precommit checks, staging, conventional commits, and optional pushes.

Official
Intermediate
shenxingyshenxingy
8

worktree

Create and manage isolated Git worktrees with TASK.md generation.

Community
Intermediate
RoentekRoentek
4

auto-stage-commit

Stage the git working tree and generate a Conventional Commits message.

Official
Intermediate