View staged vs unstaged changes

I must show Aisha and the lead how staged changes differ from my working edits before I push. Produce a concise note and a command list they can run: show which files are staged, which are modified but unstaged, and for two example files present side-by-side hunks of staged versus unstaged content so they can see what will be committed versus what won’t.

Before I create the commit for review, make it easy for the reviewer to accept only the staged work: surface the intent of the staged changes at the top, identify any unstaged edits that would confuse the reviewer, and suggest how to split remaining edits into a follow-up commit. Recommend exact commit message wording and what to call the follow-up change.

I pushed a commit that I thought included my fix, but the build server failed and the logs show the fix is missing. I don’t know whether I forgot to stage or I committed the wrong files. Explain how to quickly check my last push against my local staged and unstaged state, the commands to recover if I committed empty or wrong content, and the single-sentence status I should send to the team while I fix it.

Over the past month I’ve pushed three PRs that were missing intended edits because I mixed staging with WIP. Recommend a simple routine and two short commands I should run before every commit to avoid this, plus a naming convention for WIP edits so reviewers aren’t surprised. Keep it lightweight for a small fast-moving team.