commit-message

Generate conventional git commit messages and stage relevant files.

8|1|Updated Sep 19, 2008
One-click install
npx skills add https://github.com/juvenal/openrender --skill commit-message-juvenal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/juvenal/openrender/tree/main/.claude/skills/commit-message
Command: npx skills add https://github.com/juvenal/openrender --skill commit-message-juvenal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually writing git commit messages that match a repository's established format is time-consuming and prone to inconsistency, making project history hard to navigate and audit.

Core Features & Use Cases

  • Conventional Commit Formatting: Automatically generates commit messages that follow the repository's existing style, with a conventional commit type prefix and structured body grouped by change category.
  • Safe File Staging: Stages only relevant modified files, automatically excluding secrets, build artifacts, IDE workspace files, and other non-commitable content.
  • Use Case: After fixing a batch of compiler warnings across multiple source files in the openRender repository, this skill will generate a properly formatted commit that groups changes by warning type, matches the repo's existing commit style, and stages only the modified source files without including build outputs.

Quick Start

Use the commit-message skill to stage your recent code changes and create a properly formatted git commit that matches this repository's established message style.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I automate conventional commit messages for my git repository?

You can automate conventional commit messages by generating a type-prefixed subject line and a structured body grouped by change category. This enforces repository-compliant formatting to eliminate inconsistent git history and improve project auditability.

What is the best way to stage only relevant modified files for a git commit?

The best way to stage modified files for a git commit is to explicitly select relevant source code changes while automatically excluding build artifacts, secrets, and IDE workspace files, ensuring a safe and clean repository history.

How do I match my new commit message style to an existing repository's conventions?

Matching your commit message style to existing repository conventions requires analyzing the project's current git history. This ensures new entries for code fixes, feature additions, and build updates adhere to established formatting rules.

Can I group git commit changes automatically by category like fixes and features?

Yes, you can group git commit changes by category by structuring the commit body into sections for code fixes, feature additions, and build system updates. This categorization maintains a clean, navigable version control history.

How do I prevent sensitive files and build artifacts from being included in my git commits?

To prevent sensitive files and build artifacts from entering git commits, filter staged files to exclude secrets, IDE workspace configurations, and compiled outputs. This ensures only relevant source code modifications are committed.