commitlisted

<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. --> # Commit Changes Help the user commit code changes with a well-crafted commit message derived from the diff, following the conventions already established in the repository. ## Guidelines - **Never amend existing commits** without asking. - **Never force-push or push** without explicit user approval. - **Never skip pre-commit hooks** (do not use `--no-verify`). - **Never skip signing commits** (do not use `--no-gpg-sign`). - **Never revert, reset, or discard user changes** unless the user explicitly asked for that. - Check for obvious secrets or generated artifacts that should not be committed. If something looks risky - ask the user. - When in doubt about staging, convention, or message content — ask the user. ## Workflow ### 1. Discover the repository's commit convention Run the following to sample recent commits and the user's own commits: ``` # Recent repo commits (for overall style) git log --oneline -20 # User's recent commits (for personal style) git log --oneline --author="$(git config user.name)" -10 ``` Analyse the output to determine the commit message convention used in the repository (e.g. Conventional Commits, Gitmoji, ticket-prefixed, free-form). All generated messages **must** follow the detected convention. ### 2. Check repository status ``` git status --short ``` - If there are **no changes** (working tree clean, nothing sta