amio/dot-agents/commit-changes

Commit Changes

Review the selected Git change set, create exactly one commit, and report what was committed. An explicit request to commit or invocation of this skill authorizes that commit. Use repository state as the primary source of truth and the conversation to resolve scope and terminology.

Workflow

1. Read applicable repository instructions and inspect git status --short.

Select the change set:

• Honor a scope explicitly named by the user.
• Otherwise, if staged changes exist, select only those changes and leave

unstaged and untracked changes untouched.

• Otherwise, select relevant unstaged changes, including untracked files.

Inspect untracked files before staging and exclude unrelated, generated, credential, and secret files.

1. Inspect the selected diff and relevant files enough to understand behavior,

tests, and configuration. Do not rely on a diff stat alone. Preserve unrelated work and never discard changes. If the selected scope is empty, report No changes to commit and stop.

1. Identify the dominant user-visible or architectural intent. Write a concise

Conventional Commit subject in the form <type>(<scope>): <imperative concise title>. Choose the accurate type, such as feat, fix, refactor, docs, test, chore, or perf. Add a body only for meaningful rationale, migration, behavior, or test context; use at most three bullets and wrap lines at 72 characters.

1. Stage only selected changes that are not already staged, then create one

commit with that message. If existing staged changes outside an explicitly requested scope cannot be excluded safely, stop and explain the conflict. Do not amend, push, bypass hooks, change Git configuration, or include unrelated changes. If a hook or Git command fails, stop and report it.

1. Verify the new commit and inspect the remaining working-tree status. Report

the short hash and full subject, a concise summary of what was committed, any excluded or remaining changes, and relevant verification or hook results. Make clear whether a commit was created. Never claim a change or verification result that the repository does not support.