zapdev 1.0.0 → 1.1.1

package/README.md

@@ -4,7 +4,7 @@
 
 **zapdev** is a lightweight TypeScript CLI that makes small, repetitive Git chores fast and precise.
 
-It stages changes, scans them for secrets, generates Conventional Commit messages with an OpenAI-compatible LLM endpoint, and streamlines repository cleanup.
+It stages changes, scans them for secrets, and generates Conventional Commit messages for one repository or several direct child repositories in a single review flow.
 
 ## Project Architecture
 
@@ -20,7 +20,7 @@ flowchart LR
 ```
 
 - `src/index.ts`: bin launcher; enables the V8 compile cache, then loads `cli.js`.
-- `src/cli.ts`: CLI entry; registers subcommands and opens the interactive menu.
+- `src/cli.ts`: CLI entry; registers `commit` as the default command.
 - `src/commands/`: command UI and orchestration.
 - `src/lib/`: pure logic and isolated Git, Gitleaks, and LLM side effects.
 - `src/prompts/`: LLM prompts inlined into the bundle at build time.
@@ -34,7 +34,7 @@ flowchart LR
 | `ZD_MODEL` | For `commit` | Model identifier supported by the endpoint |
 | `ZD_EFFORT` | For `commit` | Sent as `reasoning_effort`; use a value supported by your model, such as `low`, `medium`, or `high` |
 
-There are no defaults, automatic provider detection, or backup models. CLI flags override these variables. Legacy `OLLAMA_*` variables are no longer read. Other commands do not require LLM configuration.
+There are no defaults, automatic provider detection, or backup models. CLI flags override these variables. Legacy `OLLAMA_*` variables are no longer read.
 
 Requests use the OpenAI Chat Completions format over plain `fetch`, without a provider SDK. No authentication headers are sent; use an endpoint that does not require them. The endpoint and model must support `reasoning_effort`.
 
@@ -86,11 +86,18 @@ npm run build       # bundle to dist/ with esbuild
 
 ## Usage
 
-Run `zapdev` with no command to pick one from an interactive menu. Without a TTY, zapdev displays its usage instead.
+Run `zapdev` or `zapdev commit` to start the commit flow. Both accept the flags below.
 
 ### `zapdev commit`
 
-Stages all changes, scans them with Gitleaks when installed, generates a Conventional Commit message, and optionally pushes the commit.
+Stages all changes, scans them with Gitleaks when installed, generates Conventional Commit messages, and optionally pushes the commits.
+
+- **Inside a Git repository:** uses that repository only, including when launched from a subdirectory. Does not inspect child repositories.
+- **Outside a Git repository:** processes only direct child repositories. No recursive search; `node_modules` is excluded.
+- **Unified review:** generates messages in parallel, then presents every message with its repository name.
+- **Actions:** commit all, commit only a named repository, edit a named repository's message, or cancel. Editing returns to the review menu.
+
+Repositories with nothing to commit are skipped. Unselected or cancelled changes remain staged. Push confirmation is asked once for the successfully committed repositories.
 
 ```bash
 zapdev commit
@@ -106,18 +113,20 @@ zapdev commit
 | `-s, --staged`      | Commit only changes that are already staged                       |
 | `-r, --rebase`      | Rebase on upstream if the push is rejected                        |
 | `-m, --merge`       | Merge upstream if the push is rejected                            |
-| `-y, --yes`         | Skip prompts and commit directly                                  |
+| `-y, --yes`         | Skip prompts and commit all prepared repositories                 |
 
 ```bash
 zapdev commit -t feat      # force the type
 zapdev commit --staged     # leave unstaged changes untouched
 ```
 
-Before contacting the LLM endpoint, zapdev runs `gitleaks git --staged` when Gitleaks is installed. A failed scan stops the commit; when Gitleaks is absent, the scan is skipped. The staged diff is sent to the configured endpoint, which may be remote.
+Before contacting the LLM endpoint, zapdev runs `gitleaks git --staged --verbose` in each changed repository when Gitleaks is installed. A failed scan skips that repository without sending its diff; when Gitleaks is absent, the scan is skipped. The staged diff is sent to the configured endpoint, which may be remote.
+
+Failures are reported per repository while the others continue. Any failure produces a nonzero exit code.
 
 Pushing is optimistic, with no preliminary fetch. If the branch is behind upstream, `--rebase` runs `git pull --rebase`, while `--merge` runs `git pull --no-rebase --no-edit`; zapdev then retries once. Without either flag, interactive runs ask whether to rebase, merge, or quit. Runs using `--yes` or without a TTY must provide one of the flags.
 
-Without a TTY, zapdev commits automatically and only pushes when `--push` is set.
+Without a TTY, zapdev commits all prepared repositories automatically and only pushes when `--push` is set.
 
 ### Zed IDE
 
@@ -151,31 +160,10 @@ Add this entry to Zed's `keymap.json` to run the commit task with `ctrl-cmd-ente
 }
 ```
 
-### `zapdev reset`
-
-Operates on a Git repository or the direct child repositories of a directory. It fetches and prunes, switches branch, then permanently removes other local branches and linked worktrees.
-
-```bash
-zapdev reset                 # reset the current repo or direct child repos
-zapdev reset ~/dev           # reset repos under a directory
-zapdev reset -p              # switch to the principal branch without prompting
-zapdev reset -t dev          # switch to dev or fall back to the principal branch
-```
-
-| Flag                    | Description                                                        |
-| ----------------------- | ------------------------------------------------------------------ |
-| `-p, --principal`       | Switch every repo to its resolved principal branch (`origin/HEAD`) |
-| `-t, --target <branch>` | Switch to a target branch, falling back to the principal branch    |
-| `--pull`                | Pull the checked-out branch after reset without asking             |
-| `-y, --yes`             | Switch and delete without confirmation                             |
-
-Deletion is permanent. Branches are removed with `git branch -D`; worktrees are removed with `git worktree remove --force`. Without a TTY, pass `--yes` or the destructive step is refused. `node_modules` is never scanned.
-
 ### Shell Aliases
 
 ```bash
 alias commit="zapdev commit --yes"
-alias git-reset="zapdev reset --yes --principal --pull"
 ```
 
 ## Other