skills.rest
tanujsutaria
tanujsutariaCOMMUNITY
Explore all skills by this author →
GitHub

commit-formatter

Format staged changes into conventional commit messages with type, scope, and description.

1|Updated Jan 25, 2026
Search Tags:#automation#git#workflow#commit#conventional#VitalArc
One-click install
npx skills add https://github.com/tanujsutaria/VitalArc --skill commit-formatter-tanujsutaria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-formatter
Source: https://github.com/tanujsutaria/VitalArc/tree/main/.claude/skills/commit-formatter
Command: npx skills add https://github.com/tanujsutaria/VitalArc --skill commit-formatter-tanujsutaria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VitalArc teams often produce inconsistent commit messages, making it hard to track changes and review history.

Core Features & Use Cases

  • Conventional formatting: formats staged changes into type(scope): description following VitalArc conventions.
  • Authorship finalization: automatically adds Co-Authored-By when multiple authors contributed.
  • Guided workflow: validates type, scope, and description to ensure commit metadata is accurate.

Quick Start

Format the currently staged changes into a conventional commit message following VitalArc conventions.

Frequently Asked Questions about commit-formatter

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

FAQPage Schema
How do I format staged changes into a conventional commit message?▼

Co-Authored-By is included when multiple authors contribute to the staged changes. This handles authorship finalization automatically so you don't have to manually add contributor lines.

Can I use this to enforce type and scope validation for git commits?▼

Conventional commits follow the type(scope): description format. This skill enforces that structure for staged changes, ensuring consistent project history and easier change tracking across the team.

Does this work with a general-purpose agent workflow for git automation?▼

Yes, it activates when preparing to commit or when you request to commit within a forked general-purpose agent. It then formats your staged changes accordingly.

When do I need Co-Authored-By in conventional commit messages?▼

Co-Authored-By is included when multiple authors contributed to the changes. The formatter automatically adds this attribution so you don't have to manage it manually.

Related Skills

Explore More Software Engineering Skills→
shredbxshredbx

research-git-patterns

Extract implementation patterns and story context from Git history.

Community
Intermediate
MartinoPoloMartinoPolo
1

mp-commit

Stage and commit Git changes with conventional commit messages.

Community
Intermediate
aporto-techaporto-tech

Ship

Automate code shipping with branch merging, tests, version bumps, commits, and pull requests.

Official
Advanced
cbbkrd-techcbbkrd-tech

ln-742-precommit-setup

Configure Git hooks with Husky, lint-staged, commitlint, and pre-commit.

Community
Advanced