Git style

Follow the user's request and applicable project conventions. When no commit-message convention is established, use Conventional Commits 1.0.0.

This skill needs Git only for Git operations. Without repository access, help draft the proposed change or message. Do not initialize a repository or install tools as a side effect.

Understand the state

Inspect the relevant repository status, changes, and recent history when available. Identify the intended scope and existing conventions. Preserve unrelated edits and user work.

Choose branch and integration behavior from the task and project. This skill does not require a feature branch, worktree, merge commit, squash, or pull request.

Prepare focused changes

• Keep each commit coherent enough to understand and review on its own.
• Stage only intended changes, using explicit paths or selected hunks as needed. Do not scoop up unrelated changes.
• Include necessary tests and documentation with the behavior they explain.
• Verify the affected result using the project's applicable checks. Report meaningful limits and unrelated failures.
• Do not fabricate an author, signature, issue reference, or attribution trailer. Use configured identity and required project metadata.