agileflow-commit-messages

Format git commit messages using the Conventional Commits specification.

7|1|Updated Oct 16, 2025
One-click install
npx skills add https://github.com/xloxn69/AgileFlow --skill agileflow-commit-messages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agileflow-commit-messages
Source: https://github.com/xloxn69/AgileFlow/tree/main/skills/agileflow-commit-messages
Command: npx skills add https://github.com/xloxn69/AgileFlow --skill agileflow-commit-messages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Inconsistent commit messages hinder code review, changelog generation, and historical context. This skill enforces standards and respects attribution policies, ensuring a clean Git history.

Core Features & Use Cases

  • Conventional Commits: Formats messages with type, scope, subject, body, and footer, ensuring a clean and searchable Git history.
  • Attribution Policy Compliance: Checks CLAUDE.md to determine if AI attribution should be added, respecting user preferences.
  • Use Case: You're about to commit changes for a new feature. This skill formats your commit message according to Conventional Commits, includes issue references, and adds AI attribution only if allowed by your project's policy.

Quick Start

Use the agileflow-commit-messages skill to format a commit message for "fixing the user profile update bug" and ensure it follows project attribution rules.

Frequently Asked Questions about agileflow-commit-messages

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

FAQPage Schema
How do I format git commit messages with Conventional Commits?

Conventional Commits is a specification that structures commit messages with type, scope, subject, body, and footer. This skill formats your staged changes automatically, analyzing the diff to determine the commit type and scope, then presents the formatted message for your approval before committing.

How do I add AI attribution to commit messages?

The skill reads your project's CLAUDE.md file to check your attribution policy. If your policy allows AI attribution, the skill adds it as a footer in the commit message. You control whether attribution appears through your project's configuration.

What problem does enforcing commit message standards solve?

Inconsistent commit messages make code review harder, break changelog generation, and obscure project history. Conventional Commits enforces a searchable, standardized format so your Git history remains clean and queryable across your team.

Can I use this skill with existing version control workflows?

Yes. The skill applies during commit creation across any codebase that uses Git. It analyzes your staged changes and formats the message according to Conventional Commits without requiring changes to your existing workflow or repository structure.

What happens if my project doesn't have a CLAUDE.md attribution policy?

The skill formats the commit message with type, scope, subject, body, and footer according to Conventional Commits. If CLAUDE.md is absent, no AI attribution footer is added. The core formatting still applies to keep your history standardized.