skills.rest
PeterFile
PeterFileCOMMUNITY
Explore all skills by this author →
GitHub

commit-assistant

Generate standardized commit messages, PR descriptions, and release notes.

4|2|Updated Jan 16, 2026
Search Tags:#git#workflow#commit#validation#formatting#pull-request#release-notes
One-click install
npx skills add https://github.com/PeterFile/my-common-skills --skill commit-assistant-peterfile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-assistant
Source: https://github.com/PeterFile/my-common-skills/tree/main/commit-assistant
Command: npx skills add https://github.com/PeterFile/my-common-skills --skill commit-assistant-peterfile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams consistently produce well-formed commit messages, PR descriptions, and release notes, reducing review overhead and ambiguity across code changes and project releases.

Core Features & Use Cases

  • Commit message generation: Produce standardized subject lines and bodies following conventional commit rules.
  • PR description templates: Create consistent PR descriptions, including release notes formatting.
  • Release notes support: Generate user-facing release notes according to project guidelines and categories.

Quick Start

Use the commit-assistant to generate a formatted commit for a new feature change with a concise subject line.

Frequently Asked Questions about commit-assistant

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

FAQPage Schema
How do I generate conventional commit messages automatically?▼

To generate conventional commit messages automatically, this Skill maps code changes to standardized outputs, enforcing rules for subject length, imperative mood, and body wrapping to ensure consistent formatting.

Can I create consistent PR descriptions and release notes for my project?▼

Yes, you can create consistent PR descriptions and release notes by applying standardized templates, ensuring clear formatting across code reviews and project releases, reducing ambiguity and review overhead.

What is the best way to format git commit bodies with imperative mood?▼

The best way to format git commit bodies is by applying rules for imperative mood, subject length, and body wrapping, mapping inputs to standardized outputs that follow conventional commit guidelines.

Does this commit formatting workflow support projects of any size?▼

Yes, this commit formatting workflow supports software projects of any size, applying validation and formatting rules consistently across code changes, reviews, and releases to ensure standardized outputs.

How do I handle optional breaking changes in release notes formatting?▼

To handle optional breaking changes in release notes formatting, the Skill generates user-facing release notes according to project guidelines and categories, mapping inputs to standardized outputs with clear formatting.

Related Skills

Explore More Software Engineering Skills→
ceshineceshine
1

git-workflow

Generate standardized PR descriptions from git state and commit history.

Community
Advanced
product-on-purposeproduct-on-purpose
527

deliver-release-notes

Generate user-facing release notes from changelog data.

Official
Basic
mauriciodelriomauriciodelrio
3

git-usage

Enforces Git commit message, branch naming conventions via commitlint and Husky.

Community
Advanced
micaelmaltamicaelmalta
1

git-commits

Standardize Git commit messages using Conventional Commits rules.

Community
Basic