skills.rest
notorious-ai
notorious-aiOFFICIAL
Explore all skills by this author →
GitHub

committing

Generate conventional Git commit messages for Go-centric codebases.

5|1|Updated Nov 11, 2025
Search Tags:#git#version control#commit#conventional commits#go#code history
One-click install
npx skills add https://github.com/notorious-ai/claude-plugins --skill committing-notorious-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: committing
Source: https://github.com/notorious-ai/claude-plugins/tree/main/golang-dev/skills/committing
Command: npx skills add https://github.com/notorious-ai/claude-plugins --skill committing-notorious-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you write clear, concise, and conventional Git commit messages, ensuring your project history is understandable and maintainable.

Core Features & Use Cases

  • Contextual Guidance: Provides rules and examples tailored for Go projects, but applicable broadly.
  • Target & Verb Selection: Guides you in choosing the right prefix (target) and action verb for your commit.
  • Body Writing: Offers advice on when and how to write a commit message body for added context.
  • Use Case: When you've finished a feature, this Skill will help you craft a commit message like feat: implement user authentication or fix(api): resolve null pointer exception in user lookup.

Quick Start

Use the committing skill to write a commit message for your staged changes.

Frequently Asked Questions about committing

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

FAQPage Schema
How do I write conventional Git commit messages for a Go codebase?▼

You write conventional Git commit messages by identifying the commit target, selecting an appropriate verb, and structuring the message with an optional body. This generates clear history entries like 'feat: implement user authentication' for your Go packages.

What is the best way to structure a Git commit message body for added context?▼

The best way to structure a Git commit message body is to provide context explaining the 'why' behind your changes. This Skill helps you decide when a body is needed and how to format it for maximum clarity in your version control history.

Can I use this to generate commit messages for configuration files and documentation?▼

Yes, you can generate commit messages for configuration files and documentation. The Skill handles various content types including Go packages, documentation, and configuration files by applying project-specific conventions.

Does this commit message generator work with non-Go projects?▼

Yes, the commit message generator works with non-Go projects. While it provides contextual guidance and rules tailored for Go projects, the conventional commit structuring principles are applicable broadly across different codebases.

How do I choose the right prefix and action verb for my Git commit?▼

You choose the right prefix and action verb by identifying the commit target and selecting the appropriate action. This Skill guides you in choosing prefixes like 'feat' or 'fix(api)' and pairing them with verbs to craft perfect Git commit messages.

Related Skills

Explore More Software Engineering Skills→
AstrumonAstrumon

commit

Create standardized Git commits with validated type: description messages.

Community
Intermediate
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
kirvinkirvin

preflight-checks

Run project-specific linters, formatters, and type checkers on staged files.

Community
Intermediate
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced