commit

Split workspace changes into focused Conventional Commits while preserving unrelated user changes.

609|50|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/poco-ai/Agentero --skill commit-poco-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/poco-ai/Agentero/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/poco-ai/Agentero --skill commit-poco-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Messy working directories often mix features, fixes, docs, and version bumps together, making it hard to create clean, reviewable Git history without accidentally committing unrelated changes or losing user work. ## Core Features & Use Cases - Logical Change Grouping: Reads git status, staged and unstaged diffs, and recent history to group changes by purpose (feature, test, docs, release) rather than by folder. - Conventional Commits: Produces one-purpose commits with compliant titles such as feat:, fix:, docs:, and chore(release):. - Safe Staging and Verification: Uses explicit file paths or interactive patch staging instead of git add ., runs minimal per-group validation, and never amends, rebases, tags, or pushes without explicit user request. - Use Case: After a long coding session with mixed edits across source, tests, and docs, ask the agent to split everything into a clean sequence of reviewable local commits. ## Quick Start Ask the agent to split the current workspace changes into separate Conventional Commits while keeping unrelated edits untouched.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split mixed changes into multiple Git commits?

Group changes by logical purpose such as feature, test, or docs, then stage each group with explicit file paths or interactive patch mode and commit separately. This skill automates that grouping using git status and diff inspection.

What is the Conventional Commits format for Git messages?

Conventional Commits use typed prefixes like feat:, fix:, docs:, and chore(release): followed by a concise summary. Each commit should contain a single purpose so history stays reviewable and revertible.

How to avoid committing unrelated changes with git add?

Stage explicit file paths or use interactive patch staging instead of git add . to keep unrelated edits out of a commit. The skill inspects staged and unstaged diffs first to assign each change to the right group.

Does this skill push commits or create tags automatically?

No. It only creates local commits and never amends, rebases, tags, pushes, or publishes releases unless the user explicitly requests those operations.

What happens when changes cannot be cleanly split into commits?

The skill explains its proposed grouping before committing, and stops on conflicts, sensitive files, generated artifacts, or unexplainable changes, reporting the affected paths and reasons.