commit

Run build checks, analyze code changes, and generate conventional commit messages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vibe-Media-Lab/piklit --skill commit-vibe-media-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Vibe-Media-Lab/piklit/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Vibe-Media-Lab/piklit --skill commit-vibe-media-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating well-formatted Git commit messages, ensuring consistency and saving developers time.

Core Features & Use Cases

  • Automated Build Check: Ensures the project builds successfully before committing.
  • Change Analysis: Analyzes staged and unstaged changes to understand the scope of the commit.
  • Conventional Commit Generation: Suggests commit messages following the Conventional Commits specification.
  • User Approval: Allows the user to review and approve the suggested commit message before execution.
  • Use Case: After making several code changes, you can use this Skill to automatically generate a feat: commit message, review it, and commit your changes with a single command.

Quick Start

Use the commit skill to analyze changes and suggest a commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate generating conventional commit messages from git diff?

Automating conventional commit messages analyzes git diff and git status output to suggest specifications-compliant messages. It evaluates your staged and unstaged code changes to ensure the suggested commit history remains consistent and maintainable across software development workflows.

What is the conventional commits specification and why use it for git commits?

The conventional commits specification standardizes git commit messages using structured prefixes like feat: and fix:. Adopting this format ensures a maintainable commit history that clearly communicates the scope of code changes for software development workflows.

Can I review and approve a suggested commit message before running git commit?

Yes, you can review and approve the suggested commit message before execution. The workflow requires explicit user approval, allowing you to verify the generated conventional commit against your actual code changes before finalizing the git commit operation.

Does this automation run build checks before creating a git commit?

Yes, the automation runs build checks before creating a git commit. It executes build commands prior to analyzing code changes and suggesting a conventional commit message, ensuring your project builds successfully to maintain code quality standards.

How to handle unstaged and staged code changes when automating a git commit?

Handling staged and unstaged code changes involves analyzing git diff and git status output to understand the full scope of your work. The automation evaluates all code changes before suggesting a conventional commit message for your final approval.