Q: Explain the four states a file can be in inside a Git repo: untracked, modified, staged, committed. Why does Git have a separate staging area?

A file moves through these states:

• Untracked — exists in your working directory but Git has never been told about it. Shows up under "Untracked files" in git status.
• Modified (tracked) — Git knows about the file, and the working-tree version differs from what's in the last commit. Shows under "Changes not staged for commit."
• Staged — you ran git add , copying its current content into the *index* (staging area). Shows under "Changes to be committed." git commit will record exactly this snapshot.

The staging area exists so you can build the *next* commit deliberately instead of having every saved file immediately become part of it. You can edit ten files, but git add only the three related ones, then git commit a focused logical change. git add -p takes this further — letting you stage individual hunks within a file. Without the index, you'd have to commit everything at once or stash/branch around it.

• Committed — the staged content has been written into a commit object. Working tree, index, and HEAD all agree.