Smart Commits

Turn the current working tree into one or more coherent commits, then push when the repository has a configured remote. This skill is for committing existing work. It must not become a feature-editing session.

Core Rules

• Never edit product code or docs just to make a commit easier. If validation exposes a real blocker, report it and keep the working tree intact unless the user explicitly asks for a fix.
• Never stash, reset, checkout away, overwrite, or revert unrelated changes. In multi-agent repos, treat every existing change as intentional work unless the user explicitly asks otherwise.
• Preserve the user's requested boundary. If they say to leave a path, topic, or change set alone, do not stage it.
• Stage exact files or hunks intentionally. Avoid git add . unless the whole tree has been inspected and belongs in one commit group.
• Prefer conventional commit messages with a useful body explaining why the group belongs together.
• Push after committing when a remote/upstream exists. If no push destination exists, leave the commits local and say so.

Workflow