skills.rest
visualitypl
visualityplOFFICIAL
Explore all skills by this author →
Website𝕏@visualityplGitHub

commit

Review changes, plan commit messages, and seek approval before creating Git commits.

4|Updated Jan 15, 2026
Search Tags:#git#code review#version control#development workflow#commit
One-click install
npx skills add https://github.com/visualitypl/visuality-humanlayer --skill commit-visualitypl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/visualitypl/visuality-humanlayer/tree/main/.github/skills/commit
Command: npx skills add https://github.com/visualitypl/visuality-humanlayer --skill commit-visualitypl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating Git commits by ensuring user approval and adhering to best practices for commit messages, preventing accidental attribution to AI.

Core Features & Use Cases

  • Structured Commit Creation: Guides the AI through reviewing changes, planning commits, and presenting them for user approval before execution.
  • Best Practice Adherence: Enforces imperative mood, clear descriptions, and avoids AI attribution in commit messages.
  • Use Case: After completing a set of coding tasks, you can use this Skill to help you create clean, well-documented Git commits that accurately reflect the changes made.

Quick Start

Use the commit skill to create a git commit for the recent changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit creation while reviewing the message first?▼

To create git commits with user approval, the AI reviews changes, plans a commit message, and asks for your approval before execution. This structured code version control workflow prevents accidental or unwanted commits.

Can I enforce best practices for git commit messages automatically?▼

Yes, enforcing best practices for git commit messages is handled by checking for imperative mood and clear descriptions while preventing AI attribution. This maintains clean, professional version control history without manual formatting checks.

How do I prevent AI attribution in my git commits?▼

You can prevent AI attribution in git commits by using a structured commit creation process that explicitly avoids AI attribution in the message. This ensures your version control history accurately reflects human authorship and intent.

What is the best way to structure code version control for development workflows?▼

The best way to structure code version control is to use a workflow that reviews changes, plans commits, and seeks user approval before execution. This facilitates clean, well-documented git commits that accurately reflect completed coding tasks.

Does this commit creation process support imperative mood in messages?▼

Yes, the commit creation process supports imperative mood by enforcing it during message planning. It ensures adherence to best practices by requiring imperative mood and clear descriptions while avoiding AI attribution before user approval.

Related Skills

Explore More Software Engineering Skills→
RenkunzhaoRenkunzhao
27

commit

Summarize git repository changes and generate Conventional Commit candidates.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
visualityplvisualitypl
4

describe_pr

Generate pull request descriptions from code diffs and commit history.

Official
Advanced
phucle297phucle297

caveman-commit

Generate concise conventional commit messages for Git repositories.

Community
Intermediate