commitlisted

# Commit Skill Use this skill when the work is already implemented and the next step is to create a clean git commit. ## Goals - Keep the commit scoped to the intended change - Write a concise, descriptive commit message - Avoid including unrelated modified files ## Workflow 1. Inspect the working tree before committing. 2. Confirm which files belong to the requested change. 3. Detect the repository's commit-message rules and style. 4. Stage only the relevant files. 5. Write a commit message that follows the detected style and summarizes the user-visible change. 6. Create the commit without rewriting unrelated history. ## Commit Message Style Before writing the message, check for explicit rules in repository instructions such as `AGENTS.md`, `CONTRIBUTING.md`, `README.md`, pull request templates, package scripts, or commitlint configuration. Explicit project or user rules override history. If no explicit rule exists, inspect recent commits: ```bash git log --format=%s -n 20 git log --format=%B -n 5 ``` Use the dominant style from relevant recent history: - **Conventional commits:** use `type(scope): subject` or `type: subject` when recent history uses prefixes such as `feat:`, `fix:`, `docs:`, `chore:`, `ci:`, `refactor:`, or scoped variants. - **Simple subjects:** use a concise imperative subject such as `Update skill validation workflow` when history uses plain sentence-style commit subjects. - **Multiline commits:** include a blank line and body when