Commit code changes

I changed the token expiry logic in auth/rotation.go and updated tests. Stage only the modified files auth/rotation.go and auth/rotation_test.go, write a commit message that starts with 'auth: rotate tokens —' followed by a concise summary of the change and the issue number #342, and commit to my feature branch feature/token-rotation. Ensure the commit author is my work account and not my personal one.

Before I commit these changes, make the commit easy for code review. Break the work into an atomic commit that contains the implementation change and a separate commit for test adjustments if possible, add a one-sentence header summarizing intent, a short body describing why the change was needed and its effect on backwards compatibility, and mention related issue #342. Highlight any large refactors or TODOs that should make a reviewer pause.

I staged many files while working across auth and session packages and now I'm uncertain which belong to this logical change. I fear I will accidentally include unrelated formatting or vendor updates. What is the best way to inspect and clean the staged set so the commit remains focused and reviewers aren't confused?

Across projects my commits frequently mix formatting, dependency bumps, and feature code, which slows reviews and causes rollbacks. What concrete habit and lightweight pre-commit checks should I adopt to keep commits focused, improve review turnaround, and avoid failing CI later?