docs(README): docs: update README with push confirmation flow

Author: AaronSaikovski

README.md

@@ -17,7 +17,7 @@ This project is a Rust implementation of the Go based git-cmd project found [her
 - 🤖 **AI-powered**: Uses OpenAI models (default: `gpt-4.1-mini`) to analyze code changes
 - 📝 **Conventional Commits**: Generates messages in the `type(scope): description` format
 - 🎯 **Smart Analysis**: Understands code changes and suggests contextually appropriate messages
-- ✅ **User Confirmation**: Asks for y/n confirmation before committing
+- ✅ **Push Confirmation**: Asks for y/n confirmation before pushing to remote
 - ⚡ **Interactive**: Opens your editor for final review and editing before committing
 - 📦 **Auto-staging**: Automatically stages all changes with `git add .` before analysis
 - 🔍 **Diff-aware**: Analyzes changes to generate contextually appropriate messages
@@ -70,9 +70,10 @@ sudo mv target/release/git-cmt-rs /usr/local/bin/git-cmt-rs
    ```bash
    git-cmt-rs
    ```
-2. Review the generated commit message and confirm (y/n).
-3. If confirmed, the editor opens for final review and editing.
-4. Save and close the editor to complete the commit.
+2. The editor opens for final review and editing of the commit message.
+3. Save and close the editor to create the commit.
+4. After commit, confirm whether to push to remote (y/n).
+5. If confirmed, changes are pushed; if declined, commit stays local.
 
 The tool automatically stages all changes with `git add .` before analyzing and generating a commit message.
 
@@ -82,9 +83,10 @@ The tool automatically stages all changes with `git add .` before analyzing and
 2. **Diff Analysis**: Reads staged changes with `git diff --cached -b` (truncated to 3072 chars if necessary)
 3. **AI Processing**: Sends the diff to OpenAI with structured prompts and JSON schema enforcement
 4. **Message Generation**: Produces a commit object with `type`, `scope`, and `message`
-5. **User Confirmation**: Displays the generated message and asks for confirmation (y/n)
-6. **Interactive Commit**: Opens your editor with the message for final review and editing (if confirmed)
-7. **Final Commit**: Runs `git commit` with the approved message
+5. **Interactive Commit**: Opens your editor with the message for final review and editing
+6. **Create Commit**: Runs `git commit` with the approved message
+7. **Push Confirmation**: Asks user to confirm push to remote (y/n)
+8. **Final Push**: Runs `git push` if confirmed, or exits with commit saved locally if declined
 
 ## Commit Message Format
 
@@ -98,47 +100,49 @@ type(scope): description
 
 ## Examples
 
-### Feature Addition
+### Feature Addition (Push Confirmed)
 
 ```bash
 $ git-cmt-rs
 Staged all changes with `git add .`
 Staged diff found; generating message for changes...
 Parsed commit: type='feat', scope='auth', message='add OAuth2 login integration'
 
-Generated commit message:
-  feat(auth): add OAuth2 login integration
-
-Proceed with commit? (y/n): y
 # Opens editor for final review
-# Save and close to complete the commit
+# Save and close editor to commit
+
+Commit created successfully.
+Push commit to remote? (y/n): y
+Changes pushed successfully!
 ```
 
-### Bug Fix
+### Bug Fix (Push Declined)
 
 ```bash
 $ git-cmt-rs
 Staged all changes with `git add .`
 Staged diff found; generating message for changes...
 Parsed commit: type='fix', scope='api', message='resolve null pointer in validation'
 
-Generated commit message:
-  fix(api): resolve null pointer in validation
+# Opens editor for final review
+# Save and close editor to commit
 
-Proceed with commit? (y/n): n
-Commit cancelled.
+Commit created successfully.
+Push commit to remote? (y/n): n
+Push cancelled. Commit saved locally.
 ```
 
-### Declining the Commit
+### Keeping Commit Local
 
-Users can respond with `n` or `no` to cancel the commit without opening the editor:
+Users can respond with `n` or `no` at the push confirmation to keep the commit local without pushing to remote:
 
 ```bash
 $ git-cmt-rs
 Staged all changes with `git add .`
 ...
-Proceed with commit? (y/n): n
-Commit cancelled.
+Commit created successfully.
+Push commit to remote? (y/n): n
+Push cancelled. Commit saved locally.
 ```
 
 ## Configuration
@@ -157,8 +161,10 @@ Commit cancelled.
 - **Missing API key** → exits with message to set `OPENAI_API_KEY`
 - **API failures** → shows HTTP status and response body
 - **Invalid JSON** → shows raw model output for debugging
-- **User cancellation** → exits gracefully with "Commit cancelled." when user responds with `n` or `no`
-- **Invalid confirmation input** → prompts user to answer `y/n` again
+- **Commit creation failed** → exits with error message if `git commit` fails
+- **Push declined** → exits gracefully with "Push cancelled. Commit saved locally." when user responds with `n` or `no`
+- **Push failed** → shows error if `git push` fails (commit is already saved locally)
+- **Invalid push confirmation input** → prompts user to answer `y/n` again
 
 ## Development
 
@@ -212,7 +218,14 @@ This project is open source. See the repository for details.
   export EDITOR="code --wait"
   ```
 
-**"Commit cancelled" message**
+**"Push cancelled. Commit saved locally." message**
+
+- This is expected behavior. The user can respond `n` or `no` at the push confirmation prompt to keep the commit local.
+- The commit is already created and saved; the push is simply skipped.
+- You can push manually later with `git push`.
+
+**"Push failed" error**
 
-- This is expected behavior. The user can respond `n` or `no` at the confirmation prompt to cancel the commit without opening the editor.
-- The tool exits gracefully without making any changes to the repository.
+- The commit was created successfully, but the push to remote failed (network issues, authentication, etc.)
+- Your commit is safely saved locally
+- You can try pushing again manually or resolve any issues before retrying

src/main.rs

@@ -209,13 +209,9 @@ fn build_commit_line(commit: &Commit) -> String {
     out
 }
 
-fn confirm_commit(message: &str) -> Result<bool> {
-    eprintln!("\nGenerated commit message:");
-    eprintln!("  {}", message);
-    eprintln!();
-
+fn confirm_push() -> Result<bool> {
     loop {
-        eprint!("Proceed with commit? (y/n): ");
+        eprint!("Push commit to remote? (y/n): ");
         io::stderr().flush()?;
 
         let mut input = String::new();
@@ -267,29 +263,43 @@ async fn main() -> Result<()> {
 
     let line = build_commit_line(&commit);
 
-    // Ask for confirmation before committing
-    let should_commit = match confirm_commit(&line) {
+    // Run: git commit -e -m "<line>"
+    let status = Command::new("git")
+        .args(["commit", "-e", "-m", &line])
+        .status()
+        .context("failed to run `git commit`")?;
+
+    if !status.success() {
+        return Err(anyhow!("git commit failed with status: {status}"));
+    }
+
+    eprintln!("Commit created successfully.");
+
+    // Ask for confirmation before pushing
+    let should_push = match confirm_push() {
         Ok(confirmed) => confirmed,
         Err(e) => {
-            eprintln!("Error during confirmation: {e}");
+            eprintln!("Error during push confirmation: {e}");
             std::process::exit(1);
         }
     };
 
-    if !should_commit {
-        eprintln!("Commit cancelled.");
+    if !should_push {
+        eprintln!("Push cancelled. Commit saved locally.");
         return Ok(());
     }
 
-    // Run: git commit -e -m "<line>"
+    // Run: git push
     let status = Command::new("git")
-        .args(["commit", "-e", "-m", &line])
+        .args(["push"])
         .status()
-        .context("failed to run `git commit`")?;
+        .context("failed to run `git push`")?;
 
     if !status.success() {
-        return Err(anyhow!("git commit failed with status: {status}"));
+        return Err(anyhow!("git push failed with status: {status}"));
     }
 
+    eprintln!("Changes pushed successfully!");
+
     Ok(())
 }