Amend the last commit

I just finished writing and forgot to add a file and tweak the commit message. Amend the last commit so the repository history shows the new file and the corrected message, then verify the commit hash changed and push the update to origin on branch feature/auth with forced update only if remote matches my local HEAD first.

Before I amend the last commit that others might fetch, make it safe to review: show the exact file list I’m about to include, surface the line in the message I’m changing, warn if anyone else has pushed to origin/feature/auth since my last pull, and provide a clean one-line message that preserves ticket ABC-123 and clarifies the bugfix.

I committed on branch feature/auth and need to add config/credentials.yml and tweak the message to reference ABC-123. I’m worried teammates may have fetched or based work on the old commit. What’s the safest sequence to amend locally, check for remote divergence, and update origin without blowing up others’ work?

Over the last month I keep amending the last commit to fix tiny issues and force-pushing to feature branches. It confuses reviewers and occasionally breaks colleagues’ rebases. Which habit should I change to keep history cleaner and avoid disrupting others, and what concrete rules should I adopt when altering pushed commits?