commit

Plan and create user-approved git commits with documented reasoning trails.

1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/tfunk1030/vibe --skill commit-tfunk1030
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/tfunk1030/vibe/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/tfunk1030/vibe --skill commit-tfunk1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers ensure every commit is deliberate, approved by the user, and free from attribution to external assistants.

Core Features & Use Cases

  • Structured planning: Identify and group related changes into logical commits with targeted messages.
  • Approval-driven commits: Require user confirmation before executing commit actions.
  • Reasoning trail: Document per-commit reasoning and files changed for auditability.
  • Non-attribution policy: Ensure no assistant attribution is included in commits or messages.

Quick Start

Plan your changes, confirm the plan, and generate approved commits with an auditable reasoning trail.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create clean git commits with an auditable history?

Clean git commits with an auditable history are created by enforcing explicit commit planning, targeted file selection, and user approval before execution. This workflow logs reasoning steps for each commit to maintain a clear, auditable project history.

How do I group multiple modified files into logical git commits?

Grouping multiple modified files into logical git commits requires structured planning to identify related changes and generate targeted commit messages. This ensures every commit is deliberate, properly documented, and approved by the user before execution.

Can I require user approval before executing git commit actions?

Yes, an approval-driven workflow requires explicit user confirmation before executing git commit actions. This ensures every commit is deliberate, properly documented, and prevents unauthorized or accidental commits to your project history.

Why should I exclude AI attribution from my git commit messages?

Excluding AI attribution from git commit messages enforces a non-attribution policy that keeps your project history clean and professional. This ensures commits reflect deliberate user-approved actions without external assistant references.

Does this git commit workflow work for development sessions with many file changes?

Yes, this git commit workflow is designed for development sessions where multiple files are modified. It applies planned, explicit commits with specific file selection and targeted messages to manage complex changes while maintaining an auditable reasoning trail.