commit

Generates Conventional Commits messages with ticket IDs extracted from git branch names.

1|Updated Jul 18, 2025
One-click install
npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill commit-adelysalberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/AdelysAlberto/md-configs-and-agents/tree/main/agents-copilot/skills/commit
Command: npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill commit-adelysalberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured git commit messages is repetitive and error-prone, especially when teams require ticket IDs and Conventional Commits formatting. This Skill automates staging, diff analysis, and message drafting so every commit follows the same standard. ## Core Features & Use Cases - Automatic Ticket ID Extraction: Pulls the 6-digit ticket ID from the current branch name (e.g., feature/264099 becomes #264099) and prefixes it to the commit title. - Conventional Commits Formatting: Generates titles using valid types (feat, fix, refactor, perf, style, test, docs, chore) with scope and imperative descriptions. - Structured Commit Body: Produces a conceptual summary plus a bulleted list of improvements and fixes, without listing files one by one. - Use Case: After finishing a bug fix on branch 264099-fix-grid, type /commit and the Skill stages changes, analyzes the diff, and creates a commit like #264099 fix(grid): correct column alignment with a structured technical body. ## Quick Start Type /commit to stage your current changes and generate a structured Conventional Commits message with the ticket ID from your branch.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a Conventional Commits message automatically?▼

Type /commit or /git-add and the Skill stages your changes, analyzes the diff with git diff --cached, and drafts a title using valid types like feat, fix, or refactor followed by a structured body with a summary and improvements list.

How to include a ticket ID in git commit messages?▼

The Skill extracts a 6-digit ticket ID from your current branch name, such as #264099 from feature/264099 or 264099-fix-grid, and prefixes it to the commit title. If no numeric ID exists in the branch, the prefix is omitted.

Does the commit skill push changes to the remote repository?▼

No, by default the commit stays local so you keep full control. A push to origin only happens when you explicitly request it or pass the corresponding flag.

What commit types does Conventional Commits support?▼

The Skill supports feat, fix, refactor, perf, style, test, docs, and chore. Each title follows the format type(scope): imperative description, prefixed with the ticket ID when available.

What happens if there are no staged changes when committing?▼

The Skill checks git status -s first. If no files are staged but the working tree has changes, it runs git add . or adds the relevant files before analyzing the diff and drafting the message.