guito 1.0.5 → 1.0.6

package/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to Guito are documented in this file. The project follows [S
 
 ## [Unreleased]
 
+## [1.0.6] - 2026-09-24
+
+### Added
+
+- Install Guito from Open VSX as well as the Visual Studio Marketplace. Tagged releases are now published to both registries, so VSCodium and other Open VSX-compatible editors can run the extension, and the README links to the new listing.
+- Review Azure DevOps pull requests automatically with Claude Code running on your own machine. Guito polls for the pull requests in scope (by default the active ones waiting on your review), hands each new merge source commit to Claude Code, and queues the findings in the pull request dialog's new **Review** tab, where each one shows its severity, file and line, and jumps to the diff. Tick the comments you want and post them as ordinary Azure DevOps threads, or dismiss them so they are never raised again. Nothing is posted and no vote is cast without you. When the author pushes a new commit, only the files that commit touched are reviewed again, and Claude is told what it already raised so the same point is not repeated. Configure it in the settings dialog or with the `guito.aiReview.*` VS Code settings; inside VS Code the reviewer keeps running with no Guito panel open, and **Guito: Review Pull Requests Now** checks immediately.
+
 ## [1.0.5] - 2026-09-22
 
 ### Added

package/CONTRIBUTION.md

@@ -76,15 +76,15 @@ The package is written to `vscode-extension/guito.vsix` and is ignored by Git.
 
 ## Project structure
 
-| Path | Purpose |
-| --- | --- |
-| `src/` | Angular application, components, models, utilities, and API client. |
-| `server/` | Fastify API, Git integration, and CLI server entry point. |
-| `vscode-extension/` | VS Code extension manifest, source, build script, and extension-specific docs. |
-| `tests/` | Node integration tests for the local server. |
-| `scripts/` | Release verification utilities. |
-| `bin/` | Compiled server and UI assets shipped in the npm package. |
-| `.github/workflows/` | Release automation. |
+| Path                 | Purpose                                                                        |
+| -------------------- | ------------------------------------------------------------------------------ |
+| `src/`               | Angular application, components, models, utilities, and API client.            |
+| `server/`            | Fastify API, Git integration, and CLI server entry point.                      |
+| `vscode-extension/`  | VS Code extension manifest, source, build script, and extension-specific docs. |
+| `tests/`             | Node integration tests for the local server.                                   |
+| `scripts/`           | Release verification utilities.                                                |
+| `bin/`               | Compiled server and UI assets shipped in the npm package.                      |
+| `.github/workflows/` | Release automation.                                                            |
 
 Treat `bin/`, `vscode-extension/dist/`, and packaged `.vsix` files as generated output. Make source changes under `src/`, `server/`, or `vscode-extension/src/`; do not edit generated bundles by hand. Regenerate build output with the npm scripts when it needs to be included or inspected.
 
@@ -132,7 +132,7 @@ Review feedback is part of the contribution process. Keep follow-up commits focu
 
 ## Releases
 
-Releases are maintained by the project owner. Pushing a stable `vX.Y.Z` Git tag triggers the release workflow, which verifies the root package and extension versions before building, testing, and publishing both packages. After both publishes succeed, the workflow creates the corresponding GitHub Release with generated release notes. npm uses trusted publishing, while the VS Code Marketplace publish reads the `VSCE_PAT` repository secret.
+Releases are maintained by the project owner. Pushing a stable `vX.Y.Z` Git tag triggers the release workflow, which verifies the root package and extension versions before building, testing, and publishing the npm package and extension. After every publish succeeds, the workflow creates the corresponding GitHub Release with generated release notes and attaches a versioned `.vsix` file. npm uses trusted publishing, the Visual Studio Marketplace publish reads the `VSCE_PAT` repository secret, and the Open VSX publish reads the `OVSX_PAT` repository secret.
 
 Release preparation should update:
 

package/README.md

@@ -4,7 +4,7 @@ Explore and manage Git repositories in a focused visual client. Guito runs local
 
 The name combines **GUI** and **Git**: **G**u**IT**o. It is also a [Portuguese word for money](https://dicionario.priberam.org/guito).
 
-[npm package](https://www.npmjs.com/package/guito) · [VS Code extension](https://marketplace.visualstudio.com/items?itemName=danisss9.guito) · [Issue tracker](https://github.com/danisss9/Guito/issues)
+[npm package](https://www.npmjs.com/package/guito) · [VS Code extension](https://marketplace.visualstudio.com/items?itemName=danisss9.guito) · [Open VSX extension](https://open-vsx.org/extension/danisss9/guito) · [Issue tracker](https://github.com/danisss9/Guito/issues)
 
 <img width="1848" height="941" alt="image" src="https://github.com/user-attachments/assets/680f8ca0-acbf-4c61-baf5-58cfcb6c73d1" />
 
@@ -20,6 +20,7 @@ The name combines **GUI** and **Git**: **G**u**IT**o. It is also a [Portuguese w
 - Working-tree actions for stashing changes, resetting tracked changes, and cleaning untracked files.
 - Stage and unstage files with multi-selection, preview staged and unstaged diffs, and commit staged changes.
 - Review your active Azure DevOps pull requests from the repository side panel: edit details, manage reviewers and votes, complete or auto-complete, discuss comment threads, and add inline comments on file diffs.
+- Have pull requests reviewed for you by Claude Code, re-reviewed on every new commit, with the comments queued for your approval before anything is posted.
 - Browser-based CLI and a VS Code extension with local, Remote SSH, Dev Container, and Codespaces support.
 
 > [!CAUTION]
@@ -82,6 +83,33 @@ Run the command from anywhere inside the Git worktree you want Guito to manage.
 
 The standalone server can execute Git commands against the current repository. Keep it on a trusted machine and do not expose its port to untrusted networks.
 
+## Automated pull request review
+
+Guito can hand your Azure DevOps pull requests to [Claude Code](https://claude.com/claude-code) running on your own machine, then queue what it finds for you to approve.
+
+Turn it on in **Settings** (gear icon), or with `guito.aiReview.enabled` in VS Code. Claude Code must be installed and signed in; no API key is configured in Guito, and no code leaves your machine except to the model Claude Code is already signed in to. Guito finds the CLI on `PATH`, in the standard install locations, and in the Claude Code VS Code extension's own bundled copy; set `guito.aiReview.claudePath` if yours lives somewhere else.
+
+How it works:
+
+- Guito checks Azure DevOps every few minutes for the pull requests in scope — by default the active ones that list you as a reviewer.
+- Each pull request is reviewed once per merge source commit. When the author pushes, only the files that commit touched are reviewed again, and Claude is told what it already raised so it does not repeat itself.
+- Findings land in the pull request dialog's **Review** tab, each with a severity, the file and line it is about, and the comment it would post. Tick the ones you want and choose **Post to pull request**; they become ordinary Azure DevOps comment threads from your account.
+- **Dismiss** removes a finding and stops it being raised again for that pull request.
+- Nothing is posted, and no vote is cast, without you clicking.
+
+Inside VS Code the reviewer also runs while no Guito panel is open, so pull requests are reviewed as you work; run **Guito: Review Pull Requests Now** from the Command Palette to check immediately. Reviews are stored per repository in `.git/guito-ai-reviews.json` and are never committed.
+
+| Setting                          | Description                                                                              |
+| -------------------------------- | ---------------------------------------------------------------------------------------- |
+| `guito.aiReview.enabled`         | Turns automated review on. Off by default.                                               |
+| `guito.aiReview.scope`           | `reviewer` (default), `mine`, or `all`.                                                  |
+| `guito.aiReview.pollMinutes`     | Minutes between checks. Defaults to 5.                                                   |
+| `guito.aiReview.includeDrafts`   | Also review draft pull requests. Off by default.                                         |
+| `guito.aiReview.claudePath`      | Path to the Claude Code executable. Empty means Guito looks for it (see above).           |
+| `guito.aiReview.claudeArgs`      | Extra Claude Code arguments, for example `["--model", "opus"]`.                          |
+| `guito.aiReview.timeoutSeconds`  | How long one review may take. Defaults to 600.                                           |
+| `guito.aiReview.instructions`    | Extra reviewing instructions, such as your team's conventions.                           |
+
 ## Development and contributing
 
 See [CONTRIBUTION.md](CONTRIBUTION.md) for local setup, development commands, project structure, testing, and pull-request guidance.