commit

Generate Conventional Commits messages with issue resolution links from code changes.

21|Updated May 23, 2025

Search Tags:#git #developer tools #code review #version control #commit #conventional commits

Ready to run

npx skills add https://github.com/jim60105/copilot-prompt --skill commit-jim60105

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jim60105/copilot-prompt/tree/main/skills/commit
Command: npx skills add https://github.com/jim60105/copilot-prompt --skill commit-jim60105

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Git commit messages, ensuring they adhere to the Conventional Commits specification for better project history and automation.

Core Features & Use Cases

Conventional Commits: Generates commit messages following the type: description format.
Issue Linking: Automatically appends "Resolves issue #X" when applicable.
Use Case: After completing a feature, use this Skill to generate a well-formatted commit message that clearly describes the change and links to the relevant issue tracker.

Quick Start

Use the commit skill to create a git commit message 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 generate conventional commits for staged Git changes?▼

To generate conventional commits, the Skill analyzes your staged Git changes and produces a commit message adhering to the `type: description` format for clear project history. It automatically structures the title and body based on the code differences.

Can I automatically link a Git commit message to a resolved issue?▼

Yes, you can automatically link a Git commit message to a resolved issue. The Skill appends "Resolves issue #X" to the commit body when applicable, ensuring traceability between code changes and your issue tracker.

What is the conventional commits format for Git version control?▼

The conventional commits format for Git version control uses a `type: description` structure to create clear, concise commit titles and bodies. This standard ensures consistent project history and enables automated processing of version changes.

Does this tool require external dependencies to format code review commits?▼

No, this tool requires no external dependencies to format code review commits. It operates independently to analyze code changes and generate standardized conventional commit messages without needing additional version control plugins.

When should I use an automated Git commit message generator?▼

You should use an automated Git commit message generator when finalizing code changes for version control. It is ideal for ensuring deterministic task execution, maintaining consistent conventional commits, and streamlining code review workflows.