bp-commit

Generate standardized git commits with emoji-type conventions and automatic formatting.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill bp-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bp-commit
Source: https://github.com/skaisser/blueprint/tree/main/skills/bp-commit
Command: npx skills add https://github.com/skaisser/blueprint --skill bp-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit messages are often inconsistent and can miss formatting or key details. This Skill enforces an emoji+type convention and runs code formatting before committing, improving readability and traceability of changes.

Core Features & Use Cases

  • Emoji-guided commit messages that follow a standardized schema.
  • Automatic code formatting prior to staging and committing.
  • Safe handling of operations by routing push-related commands to /bp-ship when needed.

Quick Start

Commit the current changes using the emoji-conventional commit workflow.

Frequently Asked Questions about bp-commit

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

FAQPage Schema
How do I automate formatted git commits with emoji conventions?▼

Automated git commits with emoji conventions are handled by validating local changes, formatting code per project standards, and generating a commit message using a defined emoji-type schema before staging.

What is the best way to enforce consistent git commit messages across multiple files?▼

Consistent git commit messages across multiple files are enforced by applying an emoji+type convention schema that automatically formats code and standardizes messaging before the commit is created.

Does this workflow run code formatting before staging my changes?▼

Code formatting runs automatically prior to staging and committing, ensuring all project changes meet formatting standards before the emoji-guided commit message is generated.

How do I push my changes after creating an emoji-guided commit?▼

Pushing changes after an emoji-guided commit is handled by routing push-related commands to a separate shipping workflow, keeping commit creation and remote pushing distinct.

Can I use emoji-guided commit formatting without installing external dependencies?▼

Emoji-guided commit formatting operates without external dependencies, validating local changes and applying the emoji-type schema directly within your existing version-control workflow.

Why use emoji-type conventions for version-control commit messages?▼

Emoji-type conventions for version-control commit messages improve readability and traceability of changes, solving the problem of inconsistent messages that miss formatting or key development details.