@nevzatcirak/review-mcp 2.5.2 → 2.6.0-rc.2

package/README.md

@@ -215,6 +215,7 @@ except `job_result`).
 | `pr_describe` | Describes a pull request with your LLM: a title, the change types, a short summary and a walkthrough of the changed files. The title, description, branch names, commit messages and diff are sent to your LLM endpoint. By default it only reads; `publish=true` writes to the pull request, either one comment that later runs edit in place or a marked region at the end of the description (the author's text is never changed), and `update_title=true` also replaces the title. Files the model did not describe are listed, never padded in. The pull request's issue (or `issue_context`) is used as context, without a verdict. See [Describing pull requests](docs/describe.md). |
 | `pr_improve` | Suggests code changes for a pull request with your LLM: for each suggestion the existing and the improved code, a label and a score from 0 to 10 given by a second, self-review model call; suggestions below `improve.min_score` are dropped and counted, never silently lost. Each suggestion is checked against the head version of the file before it is called anchored; ones that cannot be are marked, not hidden. The title, description, branch names, existing comments and diff are sent to your LLM endpoint, with the project's guidelines file and the listing of the touched directories read at the target branch, as for `pr_review`. By default it only reads; `publish=true` writes to the pull request: one overview comment that later runs edit in place, and an inline comment on each verified suggestion that is on changed lines of one hunk (not repeated on later runs), with the change as a native suggestion block on GitHub and GitLab and as a diff block on Gitea and Bitbucket Server. See [Suggesting code changes](docs/improve.md). |
 | `job_result` | Returns the result of a `pr_review`, `pr_ask`, `pr_describe` or `pr_improve` call that took longer than `wait_seconds` and answered with a `job_id` instead. stdio only; see [Slow endpoints](docs/review.md#slow-endpoints). |
+| CI mode (`review-mcp ci`) | A command, not a tool: reviews, describes or suggests changes for the pull request of a pipeline (GitHub Actions, Gitea Actions, GitLab CI, or any CI with `--pr-url`), prints the result, posts it with `--publish`, and exits with a documented status (`--fail-on` for a gate). The tokens come from the pipeline's secrets as `REVIEW_MCP_*`; the code under review is never built or run. See [CI mode](docs/ci.md). |
 
 The server also offers two MCP prompts:
 
@@ -237,6 +238,7 @@ The server also offers two MCP prompts:
 - [Issue compliance](docs/review.md#issue-compliance): `pr_review` checks the pull request against its issue (met, not met, needs verification) from the provider's own issues or an `issue_context` the client fetches from any tracker; budgeted, fenced, never followed as instructions; [with a tracker MCP server](docs/setup.md#with-a-tracker-mcp-server).
 - [Repository config](docs/repo-config.md): a `.review-mcp.toml` in the reviewed repository, read at the target branch, tunes its reviews (language, ignore rules, guidelines paths, toggles, tighter caps, extra instructions, default focuses, documentation style) within an allow-list that never reaches hosts, models, limits or secrets.
 - [Repository context](docs/repo-context.md): opt-in, stdio only: shows the model where the symbols a pull request changes are used elsewhere in the project (a cached `git` fetch of the head, `git grep`, a budgeted prompt block) and, optionally, lets the model read the head commit itself (repository tools); its configuration, the cache, the security properties, the coverage line and the evaluation harness.
+- [CI mode](docs/ci.md): `review-mcp ci review|describe|improve` in a pipeline: the flags, the exit codes and `--fail-on`, how the pull request is detected, the tokens with their minimal rights, examples for GitHub Actions, Gitea Actions, GitLab CI and any other CI, incremental runs, the issue context file, and pull requests from forks.
 - [Getting started](docs/getting-started.md): the minimal configuration and the diff budget in detail.
 - [Troubleshooting](docs/troubleshooting.md): the `diag` commands and every error sentence.
 - [Changelog](CHANGELOG.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nevzatcirak/review-mcp",
-  "version": "2.5.2",
+  "version": "2.6.0-rc.2",
   "description": "MCP server for AI-assisted pull-request review on Gitea and Bitbucket Server.",
   "keywords": [
     "mcp",
@@ -23,12 +23,12 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@nevzatcirak/review-mcp-linux-x64": "2.5.2",
-    "@nevzatcirak/review-mcp-linux-arm64": "2.5.2",
-    "@nevzatcirak/review-mcp-darwin-x64": "2.5.2",
-    "@nevzatcirak/review-mcp-darwin-arm64": "2.5.2",
-    "@nevzatcirak/review-mcp-win32-x64": "2.5.2",
-    "@nevzatcirak/review-mcp-win32-arm64": "2.5.2"
+    "@nevzatcirak/review-mcp-linux-x64": "2.6.0-rc.2",
+    "@nevzatcirak/review-mcp-linux-arm64": "2.6.0-rc.2",
+    "@nevzatcirak/review-mcp-darwin-x64": "2.6.0-rc.2",
+    "@nevzatcirak/review-mcp-darwin-arm64": "2.6.0-rc.2",
+    "@nevzatcirak/review-mcp-win32-x64": "2.6.0-rc.2",
+    "@nevzatcirak/review-mcp-win32-arm64": "2.6.0-rc.2"
   },
   "files": [
     "bin/review-mcp.js",