vibe-commit

Stage selected files and hunks into a single logical commit.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill governs the execution of a commit when the user requests to save vibe-coding changes, deciding which files belong in the commit, excluding generated or unwanted changes, and handling multi-line messages and trailers.

Core Features & Use Cases

  • Decide the exact files and hunks to include in a commit from a dirty working tree, ensuring a single coherent changeset.
  • Stage only the intended changes, exclude noise and generated artifacts, and verify the staged set before committing.
  • Manage commit messages and trailers safely, preserving history boundaries and avoiding unintended rewrites or pushes.
  • Enforce safety and workflow boundaries: do not push unless explicitly asked, and avoid mutating shared history.

Quick Start

Review the current changes, decide the exact file set for the commit, stage only the selected hunks, verify the staged set, and compose a safe commit message with trailers.

Frequently Asked Questions about vibe-commit

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

FAQPage Schema
How do I commit a coherent changeset from a dirty git working tree?

To commit a coherent changeset from a dirty working tree, you identify the minimal file and hunk set, explicitly stage only those changes, and verify the staged set before writing your commit message.

What is the best way to exclude generated artifacts when staging git changes?

To exclude generated artifacts when staging git changes, you select specific hunks and files explicitly, ensuring you stage only the intended changes while leaving unwanted generated files unstaged.

How do I add trailers to a git commit message safely?

To add trailers to a git commit message safely, you craft a durable commit message and append the appropriate trailers, ensuring no pushes or history rewrites occur unless explicitly requested.

Does staging individual hunks prevent unwanted files from entering the commit?

Staging individual hunks prevents unwanted files from entering the commit by allowing you to explicitly include or exclude specific changes, ensuring a single coherent changeset without generated noise.

Why should I verify the staged set before committing git changes?

Verifying the staged set before committing git changes guarantees it contains only the intended files and hunks, preventing accidental inclusion of generated artifacts or incomplete changesets.

Can this git commit workflow push changes or rewrite history automatically?

This git commit workflow does not push changes or rewrite history automatically; it enforces safety boundaries to preserve shared history unless explicitly requested by the user.