b2c-android-create-commit

Generates Git commit messages and commits changes for Android projects using .docs/commit-convention.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2c-android-create-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-android-create-commit
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2c-Android/create-commit
Command: npx skills add https://github.com/herren-official/product-agents --skill b2c-android-create-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of commit messages from your staged and unstaged changes, ensuring consistent, readable logs.

Core Features & Use Cases

  • Analyze diff and staged changes to propose concise messages that reflect the logical change.
  • Enforce project commit conventions by adhering to rules documented in .docs/commit-convention.md.
  • Automatically commit with a small, focused change message to support clean history.

Quick Start

Run this skill to analyze your current workspace and create a commit with an automatically generated message.

Frequently Asked Questions about b2c-android-create-commit

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

FAQPage Schema
How do I auto-generate a git commit message from staged and unstaged changes?

To auto-generate a git commit message, this Skill analyzes your git status and staged diffs to propose a concise, logical change message and commits it directly to your working tree.

How does automated commit message generation work with project conventions?

Automated commit message generation works by reading rules from your .docs/commit-convention.md file and applying them to the analyzed git diff, ensuring the final commit enforces your specific project standards.

Can I use this automated commit tool for Android projects?

Yes, you can use this automated commit tool for Android projects, as it is specifically designed to analyze codebase changes and generate focused commits across Android development environments.

What is the best way to maintain a clean git history in an Android project?

The best way to maintain a clean git history is to automate commits with small, focused change messages that reflect logical changes, preventing bloated or inconsistent manual commit logs.

Does automated commit generation work without a .docs/commit-convention.md file?

The Skill is designed to enforce project commit conventions by reading rules documented in .docs/commit-convention.md, so lacking this file may bypass the convention enforcement step during commit generation.