skills.rest
marcocello
marcocelloCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

coding-commit

Create coherent local Git commits with Conventional Commit formatting.

10|1|Updated Feb 22, 2026
Search Tags:#git#version control#conventional commits#commits#staging#repository changes
One-click install
npx skills add https://github.com/marcocello/dot-codex --skill coding-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-commit
Source: https://github.com/marcocello/dot-codex/tree/main/skills/coding-commit
Command: npx skills add https://github.com/marcocello/dot-codex --skill coding-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you turn a repository's current changes into coherent local commits without guessing what to stage or how to phrase the message. It is designed for commit requests where the goal is to preserve reviewable history and avoid pushing prematurely.

Core Features & Use Cases

  • Change inspection: Reviews staged, unstaged, and relevant untracked files before deciding what belongs together.
  • Commit planning: Groups related implementation, tests, documentation, and retained proof into the smallest number of coherent commits.
  • Conventional Commit writing: Produces clear local commit messages that describe the outcome, not just the mechanics.
  • Safety constraints: Never pushes, preserves coherent staged work, and asks before rewriting ambiguous staging.
  • Use case: Use this Skill when you want an AI to inspect your worktree, stage the right files, and create one or more local commits for a feature, fix, docs change, or cleanup.

Quick Start

Ask the assistant to inspect the repository changes and create the smallest set of coherent local Conventional Commits, without pushing.

Frequently Asked Questions about coding-commit

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

FAQPage Schema
How do I group unstaged and untracked files into coherent local commits?▼

To group unstaged and untracked files into coherent local commits, inspect the worktree changes to stage related implementation, tests, and documentation together, preserving reviewable boundaries.

How do I write conventional commit messages for multiple repository changes?▼

Writing conventional commit messages for repository changes involves grouping related files and applying scope-aware formatting to describe the outcome, ensuring the local commit history remains clear and reviewable.

Can I use an AI assistant to stage files and plan commits without pushing?▼

Yes, you can use an AI assistant to stage files and plan commits without pushing, as the process is designed to preserve coherent local work and strictly refuses to push changes to the remote repository.

What is the best way to handle ambiguous staging when preparing commits?▼

The best way to handle ambiguous staging when preparing commits is to ask before rewriting any existing staged work, ensuring that coherent staged boundaries are preserved and not destructively overwritten.

When do I need to create separate commits for tests and documentation?▼

You need to create separate commits for tests and documentation when changes span multiple logical areas, grouping them into the smallest number of coherent local commits to maintain a reviewable history.

Related Skills

Explore More Software Engineering Skills→
dorriodorrio

ln-003-push-all

Commit and push all local changes to the remote repository.

Community
Basic
vineet-codes256vineet-codes256

compose-and-push-commits

Organize staged and unstaged changes into atomic git commits and push them.

Community
Advanced
joseph-c-mcguirejoseph-c-mcguire
1

06-tech-tooling

Set up and validate linters, formatters, and test runners for CI builds.

Community
Advanced
JavierLianoRiozJavierLianoRioz
3

git-commit

Generate conventional Git commit messages from code diffs with intelligent file staging.

Community
Intermediate