git-commit

Create Conventional Commits messages referencing GitHub issues.

1|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/OpalBolt/Personal-AI-Marketplace --skill git-commit-opalbolt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/OpalBolt/Personal-AI-Marketplace/tree/main/plugins/productivity/skills/git-commit
Command: npx skills add https://github.com/OpalBolt/Personal-AI-Marketplace --skill git-commit-opalbolt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures your git commits adhere to the Conventional Commits standard, reference GitHub issues, and maintain a clear, informative history.

Core Features & Use Cases

  • Commit Message Guidance: Provides rules for crafting subject lines and body content, enhancing readability and maintainability.
  • Issue Number Verification: Prompts for issue number confirmation to maintain traceability of changes.
  • Automated Commit Process: Automates the git commit process based on predefined guidelines.
  • Use Case: Before committing changes, the skill assists in understanding the changes made, ensuring the correct issue reference, and composing an appropriate commit message.

Quick Start

Use the git-commit skill before running git commit to generate a well-formed commit message following the Conventional Commits format.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write git commit messages that follow Conventional Commits?

To write git commit messages following Conventional Commits, you need structured subject lines and body content. This Skill guides you in crafting well-formed messages that enhance readability and maintainability before you run the commit command.

How do I link a git commit to a specific GitHub issue?

To link a git commit to a specific GitHub issue, the Skill prompts you for issue number confirmation. This verifies the reference and maintains traceability of changes in your code history during the automated commit process.

Do I need the git command-line tool to automate commit message generation?

Yes, you need the git command-line tool installed to automate commit message generation. The Skill requires access to the git environment and GitHub issues to validate references and execute the commit process based on predefined guidelines.

What is the best way to ensure my code history traceability when committing changes?

The best way to ensure code history traceability is by validating issue references and using Conventional Commits. This Skill assists in understanding your changes and composes appropriate messages that maintain a clear, informative project history.

Can I use this Skill to automate the entire git commit process?

Yes, you can use this Skill to automate the git commit process based on predefined guidelines. It validates your changes, confirms the correct issue reference, and generates a well-formed commit message following the Conventional Commits format.