commit

name	commit
description	Creates commits using Oinkoin's conventional commit style without generated co-author or assistant footers.
argument-hint	[optional summary]

Skill: commit

Use this skill when the user asks to commit or push changes.

Commit message style

• Follow the repository's Conventional Commits style:
  • feat: ... for new functionality
  • fix: ... for bug fixes
  • refactor: ... for code restructuring
  • docs: ... for documentation
  • test: ... for tests
  • chore: ... for maintenance
• Use lowercase type and a concise imperative summary.
• Focus the summary on why the change exists, not a list of files.
• Add a short body only when the motivation or impact needs clarification.
• Do not add an issue number unless the user provides one.

Required footer policy

• Do not add Co-Authored-By lines.
• Do not add Co-authored-by lines with any capitalization.
• Do not add Generated with, Generated by, assistant attribution, bot attribution, emoji, or similar generated footers.
• Do not add any footer unless the user explicitly requests one.
• The commit message must end after the summary or explanatory body.

Commit and push workflow

1. Review both staged and unstaged changes before committing.
2. Inspect recent commit messages and match their style.
3. Stage only files related to the user's request; leave unrelated pre-existing changes unstaged.
4. Check the staged diff and git diff --cached --check.
5. Create one focused commit unless the user asks for multiple commits or the changes are clearly independent.
6. Never force-push.
7. If pushing is rejected because the remote has new commits, stop and ask whether to rebase or merge; do not choose automatically.
8. Do not amend or rewrite an existing commit unless the user explicitly requests it.