Commit changes

Commit the changes owned by the current request. Treat explicit invocation as authorization to create commits, while leaving the remote untouched.

Understand the current status, diff, and recent commit style before staging. Separate unrelated concerns into commits that can be understood, reverted, or cherry-picked independently; keep a behavior and the tests that establish it together when they form one change.

Preserve work outside the request. Leave pre-existing or ambiguously owned changes unstaged and ask only when their ownership prevents a safe commit. Exclude credentials, secrets, private keys, and environment files unless the user explicitly establishes that a particular file is safe and intended for version control.

Use Conventional Commit messages that describe the actual diff and fit the repository's history. Honor repository hooks and repair failures caused by the current change; a failed hook is evidence to address, not a check to bypass.