git-automator

Generate conventional commit messages, changelogs, and pull request descriptions from git history.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/mk-knight23/AI-Agent-Nanobot --skill git-automator-mk-knight23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-automator
Source: https://github.com/mk-knight23/AI-Agent-Nanobot/tree/main/skills/git-automator
Command: npx skills add https://github.com/mk-knight23/AI-Agent-Nanobot --skill git-automator-mk-knight23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates git workflows to generate conventional commit messages from staged diffs, write changelogs from git history, and compose pull request descriptions.

Core Features & Use Cases

  • Generate conventional commit messages from staged diffs to maintain consistent history.
  • Write CHANGELOG entries from git history for releases and maintenance.
  • Create detailed pull request descriptions from branch diffs and main differences.
  • Suggest meaningful branch names based on described work and conventions.
  • Safely operate without pushing or merging until explicit confirmation.

Quick Start

Invoke the git-automator on your current repository to generate a commit message from staged changes.

Frequently Asked Questions about git-automator

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

FAQPage Schema
How do I generate conventional commit messages from staged diffs automatically?

To generate conventional commit messages from staged diffs, the Skill analyzes your staged changes and outputs standardized commit message text. It operates locally without pushing or merging until explicitly confirmed.

What is the best way to write a changelog from git history for a release?

Writing a changelog from git history involves parsing past commits to draft release notes. The Skill automates this by extracting historical changes and writing formatted entries directly into CHANGELOG.md.

How do I compose a pull request description from branch diffs?

Composing a pull request description from branch diffs requires comparing the current branch against the main branch. The Skill automates this comparison and outputs detailed PR text into .pr_description.md.

Does this git automation tool suggest branch names based on described work?

Yes, this git automation tool suggests meaningful branch names. It analyzes your described work and standard conventions to propose appropriate branch naming structures for local development.

Can I use this Skill to push commits and merge branches automatically?

No, you cannot use this Skill to push commits or merge branches automatically. It safely operates by only generating content for CHANGELOG.md and .pr_description.md, requiring explicit confirmation before any remote actions.