asapp-draft-commit-msg

Generate conventional commit messages from staged and unstaged git diffs.

Updated Apr 28, 2024
One-click install
npx skills add https://github.com/attrigo/asapp --skill asapp-draft-commit-msg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asapp-draft-commit-msg
Source: https://github.com/attrigo/asapp/tree/main/.claude/skills/asapp-draft-commit-msg
Command: npx skills add https://github.com/attrigo/asapp --skill asapp-draft-commit-msg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns recent development changes into a clear conventional commit message, reducing the time and uncertainty involved in writing meaningful git history.

Core Features & Use Cases

  • Change Analysis: Reviews session edits, staged files, and working tree diffs to identify what changed.
  • Commit Structuring: Selects an appropriate commit type, scope, and message body using conventional commit rules.
  • Breaking Change Detection: Flags removals or incompatible API changes and formats the message accordingly.
  • Use Case: After a coding session that updates authentication logic, tests, and docs, it produces a concise commit message that accurately summarizes the work.

Quick Start

Ask the skill to generate a commit message from the current session changes.

Frequently Asked Questions about asapp-draft-commit-msg

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

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

You can generate conventional commit messages by analyzing staged and unstaged git diffs to detect changes, infer scope, and format the output automatically. The Skill reviews session edits and applies conventional commit rules to produce clear messages.

What is the best way to write a git commit message after a complex coding session?

Writing a git commit message after a complex session requires analyzing modified repository modules to select a type and scope. The Skill handles this by reviewing edits across features, tests, and docs to produce a concise summary.

Can conventional commit formatting detect breaking changes in my code refactoring?

Yes, conventional commit formatting detects breaking changes during refactoring by flagging removals or incompatible API changes. The Skill identifies these modifications from diffs and formats the commit message to highlight them.

Does this commit message generator work without any external dependencies?

Yes, this commit message generator works without external dependencies, requiring only a git-based development environment. It operates directly on staged and unstaged diffs to infer scope and handle breaking-change formatting.

When do I need automated commit structuring for version control workflows?

Automated commit structuring is needed for version control workflows when you want clear git history without manual effort. It applies to feature work, bug fixes, refactors, and documentation updates by selecting the correct type and scope from session changes.