rnd-committinglisted

# Committing ## Rules 1. **One line, imperative mood.** "Fix race condition in token refresh", not "Fixed" or "Fixes" or "Fixing". 2. **50 characters or fewer.** Hard limit. If you can't fit it, you're describing too much — split the commit or be more specific. 3. **Never mention AI, LLM, agent, Claude, or any tool authorship.** Write as a human developer would. 4. **Never add Co-Authored-By lines.** 5. **Say what and why, not how.** "Fix off-by-one in pagination cursor" — not "Change `i < len` to `i <= len`". 6. **Be specific.** "Fix login redirect on expired session" — not "Fix bug" or "Update auth". 7. **No filler words.** Drop "various", "some", "minor", "small". Every word must carry information. 8. **Don't explain framework internals.** Never reference skills, hooks, pipeline phases, or orchestration mechanics. Describe the user-visible change. 9. **Don't assume GitHub.** The remote could be GitLab, Gitea, Codeberg, Forgejo, Tangled, or any other host. Check `git remote get-url origin` before using platform-specific CLI tools (e.g., `gh` is GitHub-only). For PRs/MRs, ask the user or infer from the remote URL. ## Commit Workflow Use only git commands and dedicated Claude Code tools — use Read instead of `cat`, Grep instead of `grep`, Edit instead of `sed`, Glob instead of `find`. Prefer dedicated tools over shell equivalents — they are reviewable and produce cleaner diffs. 1. Run `git status` and `git diff` (separate Bash calls, never chained with `&&`). 2. If you n