commit

Create git commits with explicit path staging and post-commit verification.

Updated May 17, 2022
One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill commit-kanade0404
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/commit
Command: npx skills add https://github.com/kanade0404/dotfiles --skill commit-kanade0404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns commit creation into a reliable, low-friction workflow that avoids unsafe bulk staging and reduces failures in restrictive environments.

Core Features & Use Cases

  • Observed First: Checks the current branch and working tree before making any changes so existing staged work is handled intentionally.
  • Safe Staging: Stages only explicitly named paths, which helps with partial commits and prevents unrelated files from being bundled accidentally.
  • Robust Commit Creation: Writes the commit message through a file and verifies the result after commit, making it suitable for guarded shells, hooks, and automated development loops.

Quick Start

Ask the skill to create a commit for the current changes with explicit staging, a clear message, and final verification.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a git commit while avoiding unsafe bulk staging of all files?

To create safe git commits, stage only explicitly named paths instead of all files. This prevents unrelated files from being bundled accidentally and ensures partial commits remain focused and deterministic.

What is the best way to automate git commits in guarded shells with hooks?

Automating git commits in guarded shells requires writing the commit message through a file and verifying the result post-commit. This approach maintains safety and determinism in automated development loops.

How do I perform a partial commit for TDD checkpoints without losing staged work?

Performing a partial commit for TDD checkpoints requires checking the current branch and working tree first. Staging only explicitly named paths ensures existing staged work is handled intentionally without being overwritten.

Can I use explicit path staging to create tidy-first increments in version control?

Yes, explicit path staging supports tidy-first increments in version control. By isolating specific file changes, you can create focused, deterministic commits that align with safe developer workflows.

Why does my automated git workflow fail in restrictive environments?

Automated git workflows often fail in restrictive environments due to unsafe bulk staging or direct command-line message passing. Using file-based commit messages and post-commit verification helps reduce these failures.

What are the limitations of using bulk staging for version-control checkpoints?

Bulk staging limits version-control checkpoints by bundling unrelated files together, which obscures commit intent. It bypasses branch-state checks and post-commit verification, reducing safety and determinism in focused workflows.