diff-commitlisted

# Git Diff Validator & Commit Title Generator When this skill is activated, analyze the current `git diff` (staged and unstaged changes), validate the diff against common quality rules, and produce a single ready-to-use commit title. ## Steps 1. Run `git diff HEAD` to capture all current changes (staged + unstaged). If the output is empty, also run `git diff --cached` to check staged-only changes. If both are empty, inform the user that there are no changes and stop. 2. Run `git status` to understand which files are affected and their state. 3. Parse the diff and validate it against all rules below. 4. Determine the dominant change type and scope from the diff. 5. Output the validation result and the generated commit title. ## Validation Rules Check each rule and record any violations: ### Code Quality - **No debug artifacts**: flag any `console.log`, `print(`, `debugger`, `binding.pry`, `dd(`, `var_dump(` lines added in the diff - **No commented-out code blocks**: flag newly added lines that consist only of commented-out code (not explanatory comments) - **No TODO/FIXME in new code**: flag newly added `TODO`, `FIXME`, or `HACK` comments - **No hardcoded secrets**: flag patterns like `password =`, `api_key =`, `secret =`, `token =` assigned to a string literal ### Diff Integrity - **Not too large**: warn if the diff exceeds 500 changed lines — large diffs are hard to review and may mix concerns - **Single concern**: warn if the diff touches more than 5 unrelated direct