When my change is done, I have to leave TuiCode to commit it

[a-team-app]

Opportunity

I finish a change in TuiCode, and the last step, committing it, is the one thing I can't do there. I leave the editor, or switch to another terminal tab. Then I run git status and git diff to remember what I touched, stage it (sometimes only part of a file), write the message, commit and push, and come back. TuiCode already shows me my changes: the gutter, Compare to saved, the Review tab and revert hunk (rc). But it stops short of letting me keep them. It happens several times a day, every time a piece of work lands, and it's the moment I most want to see my own diff one more time.

Evidence

• Nothing in TuiCode stages, commits or pushes. The git commands are compare, blame, review and revert. Suspending to the shell (Suspend to the shell and come back (instead of a terminal panel) #64) is still an Idea, so leaving means quitting or switching terminal tabs.
• Zed treated native git as a headline feature and shipped a Git panel for stage/commit (blog, docs). Its users keep pushing it further: partial staging (discussion #25949), commit + push in one step (#51183), and multi-repo workspaces (#59221).
• Helix users have asked for git actions for years (#2261, #5166, discussion #6032). A fork now adds a status picker with stage/unstage and a commit draft (samuel-lindgren/helix#11) and push (#12), which shows how much people want it in a terminal editor too.
• VS Code's Source Control view is the model the vision says TuiCode borrows from. A VS Code user expects to commit without leaving the editor.

Why it fits

• Seeing change is theme 2, and TuiCode already has the diff, gutter and review pieces. Committing is where that loop naturally closes.
• It's a daily-driver gap in the vision's sense: a routine step that sends you somewhere else.
• It fits the rules: the work runs through the git CLI that TuiCode already drives, it works the same over SSH, and it needs no extension host.
• Zed and Helix aren't named in the vision. Zed is a VS Code-style editor that made git native, and Helix is a terminal editor whose users want the same thing.

[jamescrosswell]

I don't think we should do this.

VS Code and Rider both have the ability to do this and I don't use it. I'd rather use my favourite git tool (which has changed over time but currently I like LazyGit). It's easy enough to open a separate terminal tab when running TuiCode locally and make the commit via whatever your favourite tool is there.

Let's park this as 'won't do'.