gitpr-cli 1.1.0__tar.gz → 1.2.0__tar.gz

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gitpr-cli
-Version: 1.1.0
+Version: 1.2.0
 Summary: AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)
 Author-email: Natan Fiuza <contato@natanfiuza.dev.br>
 Requires-Python: >=3.10
@@ -148,11 +148,11 @@ You can pass the following *flags* for specific actions:
 * `--status`: Lists uncommitted file changes categorized as **new**, **modified**, and **deleted** — fast, no AI, no network. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/git-status.md)
 * `--no-unstaged-check`: Skips the unstaged files verification before AI processing for a single invocation. Equivalent to `GITPR_SKIP_UNSTAGED_CHECK=true` for one run. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/git-status.md)
 * `--linter-setup`: **Interactive external linter wizard.** Guides you through installing and configuring external linters (ESLint, PHPCS, Stylelint) as a Checkstyle XML bridge. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/linter-regras-customizadas.md)
-* `--mcp`: Starts GitPR as an **MCP server** (Model Context Protocol) on stdio transport. Enables integration with VS Code, Cursor, Claude Desktop, and other MCP-compatible editors — exposing all GitPR AI capabilities as 12 annotated tools, 15 resources, and 7 pre-built prompts directly inside your IDE. Also available as the standalone `gitpr-mcp` command.
+* `--mcp`: Starts GitPR as an **MCP server** (Model Context Protocol) on stdio transport. Enables integration with VS Code, Cursor, Claude Desktop, and other MCP-compatible editors — exposing all GitPR AI capabilities as 14 annotated tools, 18 resources, and 7 pre-built prompts directly inside your IDE. Also available as the standalone `gitpr-mcp` command.
 * `--plugins`: Lists all **globally installed plugins** — custom linter packs from `~/.gitpr/plugins/linter/` and MCP prompt templates from `~/.gitpr/plugins/prompts/`. These plugins apply across all your projects without duplication. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/plugins-system.md)
 * `--install`: **Interactive Setup Wizard.** Runs a guided 4-step setup: downloads skill templates, installs Git hooks, configures MCP for detected editors, and checks/requests your AI provider API key. Each step asks for confirmation before proceeding.
 * `-ih` or `--installhooks`: Automatically installs **local Git Hooks** (`pre-commit` and `prepare-commit-msg`) in your repository.
-* `-s` or `--skill`: Creates the AI context template files (`.gitpr.commit.md`, `.gitpr.pr.md`, `.gitpr.review.md`, `.gitpr.filereview.md`, `.gitpr.issue.md`, `.gitpr.blame.md`) and the Linter (`.gitpr.linter.yml`) at the project root.
+* `-s` or `--skill`: Creates the AI context template files (`.gitpr.commit.md`, `.gitpr.pr.md`, `.gitpr.review.md`, `.gitpr.filereview.md`, `.gitpr.issue.md`, `.gitpr.blame.md`) and the Linter (`.gitpr.linter.yml`) inside `.gitpr/skill/`.
 * `-is` or `--issue`: Automatically generates a draft of a **standardized Issue** and opens an interactive interface (TUI) for editing or direct submission via REST API. This feature has **3 context engines** depending on the command combination:
   * **New Code Issue (`gitpr -is`):** Reads the current `git diff`. **Why use:** Ideal for quickly documenting the task you just finished programming, before committing.
   * **Epic/Release Issue (`gitpr -is -ht`):** Reads the full history of the current branch (Git Log + PR Cache). **Why use:** Ideal for generating consolidated documentation of an entire release or a large *feature* that took several days/commits to complete.
@@ -229,7 +229,7 @@ You can dynamically switch models by configuring the `GEMINI_API_MODEL_PRIMARY`
 
 ## 🎯 Customizable "Skills" System (Prompt Engineering)
 
-Instead of hiding AI instructions in the source code, GitPR uses local Markdown files that act as *System Instructions*. When running `gitpr -s`, the following files are generated at the root of your project to customize the AI's "persona" according to your company's business rules:
+Instead of hiding AI instructions in the source code, GitPR uses local Markdown files that act as *System Instructions*. When running `gitpr -s`, the following files are generated inside `.gitpr/skill/` to customize the AI's "persona" according to your company's business rules:
 
 * `.gitpr.commit.md`: Rules for generating short commit messages.
 * `.gitpr.pr.md`: Required topic structure for the Pull Request description.
@@ -335,6 +335,8 @@ Once configured, use natural language in your editor's AI chat:
 | `generate_issue` | Structured issue from diff, history, or blame |
 | `list_unstaged_files` | Uncommitted file changes categorized (new/modified/deleted) |
 | `analyze_unstaged_diff` | Unstaged diff only (working tree vs index) |
+| `list_fix_candidates` | Fix candidates of the last review: patch, classification, id (read-only) |
+| `review_remote_pr` | AI review of a pull request already open on the forge, fetched by number (read-only) |
 
 ### Direct CLI Invocation
 
@@ -430,12 +432,14 @@ If you want to implement GitPR as an automated quality barrier in your team, che
 
 * [**Pull Request (Default Mode)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/pr-descricao-padrao.md) — Complete flow for generating PR descriptions without flags.
 * [**Pull Request Publisher TUI**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/pull-request-publication.md) — How to review and publish Pull Requests directly to GitHub from the terminal.
-* [**AI Code Review**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/code-review-ia.md) — Guide to review modes (`--review`, `--fullreview`) and file auditing (`--input`).
+* [**AI Code Review**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/code-review-ia.md) — Guide to review modes (`--review`, `--fullreview`), file auditing (`--input`) and remote pull request review (`gitpr review-pr`).
+* [**Remote Pull Request Review (gitpr review-pr)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/review-pr.md) — How the `gitpr review-pr` subcommand reviews a pull request that is already open on the forge, fetching its diff from the API without checking out its branch.
 * [**AI Commit Messages**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/commit-message-ia.md) — How to generate messages in the Conventional Commits standard and integrate with Git Hooks.
 * [**Issue Generation and TUI Interface**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/issue-tui-help.md) — How to use the terminal graphical interface (TUI) and the 3 context engines to manage structured Issues.
 * [**Code Archaeologist (Git Blame)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/blame-arqueologo.md) — How to trace the origin of business rules with `git blame` and AI.
 * [**Skills and Templates System**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/skill-template.md) — How to customize AI behavior with `.gitpr.*.md` files.
 * [**Release Notes & Changelog (gitpr release)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/release-notes.md) — How the `gitpr release` subcommand generates the changelog / release notes of a repository, suggests the next semantic version and publishes releases on the forge.
+* [**Fix Command (gitpr fix)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/fix-command.md) — How the `gitpr fix` subcommand turns the findings of the last review into patches you read before they touch your tree, classifies each one by safety, and undoes an applied patch on demand.
 
 ### Configuration & Infrastructure
 

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/README.md

@@ -129,11 +129,11 @@ You can pass the following *flags* for specific actions:
 * `--status`: Lists uncommitted file changes categorized as **new**, **modified**, and **deleted** — fast, no AI, no network. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/git-status.md)
 * `--no-unstaged-check`: Skips the unstaged files verification before AI processing for a single invocation. Equivalent to `GITPR_SKIP_UNSTAGED_CHECK=true` for one run. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/git-status.md)
 * `--linter-setup`: **Interactive external linter wizard.** Guides you through installing and configuring external linters (ESLint, PHPCS, Stylelint) as a Checkstyle XML bridge. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/linter-regras-customizadas.md)
-* `--mcp`: Starts GitPR as an **MCP server** (Model Context Protocol) on stdio transport. Enables integration with VS Code, Cursor, Claude Desktop, and other MCP-compatible editors — exposing all GitPR AI capabilities as 12 annotated tools, 15 resources, and 7 pre-built prompts directly inside your IDE. Also available as the standalone `gitpr-mcp` command.
+* `--mcp`: Starts GitPR as an **MCP server** (Model Context Protocol) on stdio transport. Enables integration with VS Code, Cursor, Claude Desktop, and other MCP-compatible editors — exposing all GitPR AI capabilities as 14 annotated tools, 18 resources, and 7 pre-built prompts directly inside your IDE. Also available as the standalone `gitpr-mcp` command.
 * `--plugins`: Lists all **globally installed plugins** — custom linter packs from `~/.gitpr/plugins/linter/` and MCP prompt templates from `~/.gitpr/plugins/prompts/`. These plugins apply across all your projects without duplication. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/plugins-system.md)
 * `--install`: **Interactive Setup Wizard.** Runs a guided 4-step setup: downloads skill templates, installs Git hooks, configures MCP for detected editors, and checks/requests your AI provider API key. Each step asks for confirmation before proceeding.
 * `-ih` or `--installhooks`: Automatically installs **local Git Hooks** (`pre-commit` and `prepare-commit-msg`) in your repository.
-* `-s` or `--skill`: Creates the AI context template files (`.gitpr.commit.md`, `.gitpr.pr.md`, `.gitpr.review.md`, `.gitpr.filereview.md`, `.gitpr.issue.md`, `.gitpr.blame.md`) and the Linter (`.gitpr.linter.yml`) at the project root.
+* `-s` or `--skill`: Creates the AI context template files (`.gitpr.commit.md`, `.gitpr.pr.md`, `.gitpr.review.md`, `.gitpr.filereview.md`, `.gitpr.issue.md`, `.gitpr.blame.md`) and the Linter (`.gitpr.linter.yml`) inside `.gitpr/skill/`.
 * `-is` or `--issue`: Automatically generates a draft of a **standardized Issue** and opens an interactive interface (TUI) for editing or direct submission via REST API. This feature has **3 context engines** depending on the command combination:
   * **New Code Issue (`gitpr -is`):** Reads the current `git diff`. **Why use:** Ideal for quickly documenting the task you just finished programming, before committing.
   * **Epic/Release Issue (`gitpr -is -ht`):** Reads the full history of the current branch (Git Log + PR Cache). **Why use:** Ideal for generating consolidated documentation of an entire release or a large *feature* that took several days/commits to complete.
@@ -210,7 +210,7 @@ You can dynamically switch models by configuring the `GEMINI_API_MODEL_PRIMARY`
 
 ## 🎯 Customizable "Skills" System (Prompt Engineering)
 
-Instead of hiding AI instructions in the source code, GitPR uses local Markdown files that act as *System Instructions*. When running `gitpr -s`, the following files are generated at the root of your project to customize the AI's "persona" according to your company's business rules:
+Instead of hiding AI instructions in the source code, GitPR uses local Markdown files that act as *System Instructions*. When running `gitpr -s`, the following files are generated inside `.gitpr/skill/` to customize the AI's "persona" according to your company's business rules:
 
 * `.gitpr.commit.md`: Rules for generating short commit messages.
 * `.gitpr.pr.md`: Required topic structure for the Pull Request description.
@@ -316,6 +316,8 @@ Once configured, use natural language in your editor's AI chat:
 | `generate_issue` | Structured issue from diff, history, or blame |
 | `list_unstaged_files` | Uncommitted file changes categorized (new/modified/deleted) |
 | `analyze_unstaged_diff` | Unstaged diff only (working tree vs index) |
+| `list_fix_candidates` | Fix candidates of the last review: patch, classification, id (read-only) |
+| `review_remote_pr` | AI review of a pull request already open on the forge, fetched by number (read-only) |
 
 ### Direct CLI Invocation
 
@@ -411,12 +413,14 @@ If you want to implement GitPR as an automated quality barrier in your team, che
 
 * [**Pull Request (Default Mode)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/pr-descricao-padrao.md) — Complete flow for generating PR descriptions without flags.
 * [**Pull Request Publisher TUI**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/pull-request-publication.md) — How to review and publish Pull Requests directly to GitHub from the terminal.
-* [**AI Code Review**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/code-review-ia.md) — Guide to review modes (`--review`, `--fullreview`) and file auditing (`--input`).
+* [**AI Code Review**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/code-review-ia.md) — Guide to review modes (`--review`, `--fullreview`), file auditing (`--input`) and remote pull request review (`gitpr review-pr`).
+* [**Remote Pull Request Review (gitpr review-pr)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/review-pr.md) — How the `gitpr review-pr` subcommand reviews a pull request that is already open on the forge, fetching its diff from the API without checking out its branch.
 * [**AI Commit Messages**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/commit-message-ia.md) — How to generate messages in the Conventional Commits standard and integrate with Git Hooks.
 * [**Issue Generation and TUI Interface**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/issue-tui-help.md) — How to use the terminal graphical interface (TUI) and the 3 context engines to manage structured Issues.
 * [**Code Archaeologist (Git Blame)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/blame-arqueologo.md) — How to trace the origin of business rules with `git blame` and AI.
 * [**Skills and Templates System**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/skill-template.md) — How to customize AI behavior with `.gitpr.*.md` files.
 * [**Release Notes & Changelog (gitpr release)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/release-notes.md) — How the `gitpr release` subcommand generates the changelog / release notes of a repository, suggests the next semantic version and publishes releases on the forge.
+* [**Fix Command (gitpr fix)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/fix-command.md) — How the `gitpr fix` subcommand turns the findings of the last review into patches you read before they touch your tree, classifies each one by safety, and undoes an applied patch on demand.
 
 ### Configuration & Infrastructure
 

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/gitpr_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gitpr-cli
-Version: 1.1.0
+Version: 1.2.0
 Summary: AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)
 Author-email: Natan Fiuza <contato@natanfiuza.dev.br>
 Requires-Python: >=3.10
@@ -148,11 +148,11 @@ You can pass the following *flags* for specific actions:
 * `--status`: Lists uncommitted file changes categorized as **new**, **modified**, and **deleted** — fast, no AI, no network. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/git-status.md)
 * `--no-unstaged-check`: Skips the unstaged files verification before AI processing for a single invocation. Equivalent to `GITPR_SKIP_UNSTAGED_CHECK=true` for one run. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/git-status.md)
 * `--linter-setup`: **Interactive external linter wizard.** Guides you through installing and configuring external linters (ESLint, PHPCS, Stylelint) as a Checkstyle XML bridge. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/linter-regras-customizadas.md)
-* `--mcp`: Starts GitPR as an **MCP server** (Model Context Protocol) on stdio transport. Enables integration with VS Code, Cursor, Claude Desktop, and other MCP-compatible editors — exposing all GitPR AI capabilities as 12 annotated tools, 15 resources, and 7 pre-built prompts directly inside your IDE. Also available as the standalone `gitpr-mcp` command.
+* `--mcp`: Starts GitPR as an **MCP server** (Model Context Protocol) on stdio transport. Enables integration with VS Code, Cursor, Claude Desktop, and other MCP-compatible editors — exposing all GitPR AI capabilities as 14 annotated tools, 18 resources, and 7 pre-built prompts directly inside your IDE. Also available as the standalone `gitpr-mcp` command.
 * `--plugins`: Lists all **globally installed plugins** — custom linter packs from `~/.gitpr/plugins/linter/` and MCP prompt templates from `~/.gitpr/plugins/prompts/`. These plugins apply across all your projects without duplication. 📖 [Full docs](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/plugins-system.md)
 * `--install`: **Interactive Setup Wizard.** Runs a guided 4-step setup: downloads skill templates, installs Git hooks, configures MCP for detected editors, and checks/requests your AI provider API key. Each step asks for confirmation before proceeding.
 * `-ih` or `--installhooks`: Automatically installs **local Git Hooks** (`pre-commit` and `prepare-commit-msg`) in your repository.
-* `-s` or `--skill`: Creates the AI context template files (`.gitpr.commit.md`, `.gitpr.pr.md`, `.gitpr.review.md`, `.gitpr.filereview.md`, `.gitpr.issue.md`, `.gitpr.blame.md`) and the Linter (`.gitpr.linter.yml`) at the project root.
+* `-s` or `--skill`: Creates the AI context template files (`.gitpr.commit.md`, `.gitpr.pr.md`, `.gitpr.review.md`, `.gitpr.filereview.md`, `.gitpr.issue.md`, `.gitpr.blame.md`) and the Linter (`.gitpr.linter.yml`) inside `.gitpr/skill/`.
 * `-is` or `--issue`: Automatically generates a draft of a **standardized Issue** and opens an interactive interface (TUI) for editing or direct submission via REST API. This feature has **3 context engines** depending on the command combination:
   * **New Code Issue (`gitpr -is`):** Reads the current `git diff`. **Why use:** Ideal for quickly documenting the task you just finished programming, before committing.
   * **Epic/Release Issue (`gitpr -is -ht`):** Reads the full history of the current branch (Git Log + PR Cache). **Why use:** Ideal for generating consolidated documentation of an entire release or a large *feature* that took several days/commits to complete.
@@ -229,7 +229,7 @@ You can dynamically switch models by configuring the `GEMINI_API_MODEL_PRIMARY`
 
 ## 🎯 Customizable "Skills" System (Prompt Engineering)
 
-Instead of hiding AI instructions in the source code, GitPR uses local Markdown files that act as *System Instructions*. When running `gitpr -s`, the following files are generated at the root of your project to customize the AI's "persona" according to your company's business rules:
+Instead of hiding AI instructions in the source code, GitPR uses local Markdown files that act as *System Instructions*. When running `gitpr -s`, the following files are generated inside `.gitpr/skill/` to customize the AI's "persona" according to your company's business rules:
 
 * `.gitpr.commit.md`: Rules for generating short commit messages.
 * `.gitpr.pr.md`: Required topic structure for the Pull Request description.
@@ -335,6 +335,8 @@ Once configured, use natural language in your editor's AI chat:
 | `generate_issue` | Structured issue from diff, history, or blame |
 | `list_unstaged_files` | Uncommitted file changes categorized (new/modified/deleted) |
 | `analyze_unstaged_diff` | Unstaged diff only (working tree vs index) |
+| `list_fix_candidates` | Fix candidates of the last review: patch, classification, id (read-only) |
+| `review_remote_pr` | AI review of a pull request already open on the forge, fetched by number (read-only) |
 
 ### Direct CLI Invocation
 
@@ -430,12 +432,14 @@ If you want to implement GitPR as an automated quality barrier in your team, che
 
 * [**Pull Request (Default Mode)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/pr-descricao-padrao.md) — Complete flow for generating PR descriptions without flags.
 * [**Pull Request Publisher TUI**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/pull-request-publication.md) — How to review and publish Pull Requests directly to GitHub from the terminal.
-* [**AI Code Review**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/code-review-ia.md) — Guide to review modes (`--review`, `--fullreview`) and file auditing (`--input`).
+* [**AI Code Review**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/code-review-ia.md) — Guide to review modes (`--review`, `--fullreview`), file auditing (`--input`) and remote pull request review (`gitpr review-pr`).
+* [**Remote Pull Request Review (gitpr review-pr)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/review-pr.md) — How the `gitpr review-pr` subcommand reviews a pull request that is already open on the forge, fetching its diff from the API without checking out its branch.
 * [**AI Commit Messages**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/commit-message-ia.md) — How to generate messages in the Conventional Commits standard and integrate with Git Hooks.
 * [**Issue Generation and TUI Interface**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/issue-tui-help.md) — How to use the terminal graphical interface (TUI) and the 3 context engines to manage structured Issues.
 * [**Code Archaeologist (Git Blame)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/blame-arqueologo.md) — How to trace the origin of business rules with `git blame` and AI.
 * [**Skills and Templates System**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/skill-template.md) — How to customize AI behavior with `.gitpr.*.md` files.
 * [**Release Notes & Changelog (gitpr release)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/release-notes.md) — How the `gitpr release` subcommand generates the changelog / release notes of a repository, suggests the next semantic version and publishes releases on the forge.
+* [**Fix Command (gitpr fix)**](https://github.com/gitpr-cli/gitpr.git/blob/main/docs/fix-command.md) — How the `gitpr fix` subcommand turns the findings of the last review into patches you read before they touch your tree, classifies each one by safety, and undoes an applied patch on demand.
 
 ### Configuration & Infrastructure
 

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/gitpr_cli.egg-info/SOURCES.txt

@@ -29,6 +29,7 @@ src/mcp_server.py
 src/metrics.py
 src/net.py
 src/release_engine.py
+src/reviewer_resolution.py
 src/reviewer_suggestion.py
 src/security.py
 src/spinner.py
@@ -37,6 +38,14 @@ src/tui_issue.py
 src/updater.py
 src/usage_log.py
 src/version_bump.py
+src/fix/__init__.py
+src/fix/apply_fix.py
+src/fix/fix_history.py
+src/fix/patch_applier.py
+src/fix/patch_extractor.py
+src/fix/patch_provenance.py
+src/fix/patch_safety_classifier.py
+src/fix/rollback_fix.py
 src/infrastructure/__init__.py
 src/infrastructure/scm/__init__.py
 src/infrastructure/scm/azure_devops_provider.py
@@ -45,6 +54,11 @@ src/infrastructure/scm/bitbucket_provider.py
 src/infrastructure/scm/factory.py
 src/infrastructure/scm/github_provider.py
 src/infrastructure/scm/gitlab_provider.py
+src/review/__init__.py
+src/review/diff_normalizer.py
+src/review/diff_source.py
+src/review/remote_pr.py
+src/review/render.py
 src/ui/__init__.py
 src/ui/chat_app.py
 src/ui/config_app.py
@@ -85,6 +99,7 @@ tests/test_pr_publish_linter_modal.py
 tests/test_pre_save.py
 tests/test_release_cli.py
 tests/test_release_engine.py
+tests/test_reviewer_resolution.py
 tests/test_reviewer_suggestion.py
 tests/test_skill_command.py
 tests/test_skill_context.py

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/src/cache.py

@@ -47,9 +47,22 @@ def get_cached_response(action_folder, prompt_text):
 
 
 def save_cached_response(
-    action_folder, action_type, prompt_text, response_dict, meta_raw=None
+    action_folder,
+    action_type,
+    prompt_text,
+    response_dict,
+    meta_raw=None,
+    reviewed_diff=None,
 ):
-    """Saves the AI response to the local cache."""
+    """Saves the AI response to the local cache.
+
+    ``reviewed_diff`` is the diff the review actually ran on. When given it is
+    stored at the top level of the record, so ``gitpr fix`` can re-derive its
+    patch from the revision that was reviewed instead of whatever the working
+    tree happens to hold later — the two differ whenever the review came from a
+    pull request (src/review/remote_pr.py) or from a full-branch diff. Records
+    written before this field existed simply lack it, and the reader falls back.
+    """
     md5_hash = generate_md5(prompt_text)
     folder_path = get_cache_base_dir() / action_folder
     folder_path.mkdir(parents=True, exist_ok=True)
@@ -76,6 +89,9 @@ def save_cached_response(
         "response": response_dict,
     }
 
+    if reviewed_diff is not None:
+        cache_data["diff"] = reviewed_diff
+
     try:
         with open(cache_file, "w", encoding="utf-8") as f:
             json.dump(cache_data, f, indent=2, ensure_ascii=False)
@@ -83,6 +99,51 @@ def save_cached_response(
         pass  # Silent cache failure to avoid crashing the tool
 
 
+# Review action types whose prompt is a branch diff. `filereview` is left out
+# on purpose: it audits a single file and has no diff to re-derive.
+REVIEW_ACTION_TYPES = ("review", "fullreview")
+
+
+def resolve_last_review(repo_name, branch_name):
+    """The most recent cached review for *repo_name* and *branch_name*, or None.
+
+    All three review modes write into the same ``review/`` folder (see
+    ``core.generate_pr_content``), so ``action_type`` is what tells them apart —
+    without that filter a file audit would be mistaken for a branch review.
+
+    Returns the cache record itself: the caller reads
+    ``record["response"]["review"]`` for the text and ``record["action_type"]``
+    to know which diff produced it, so the patch can be re-derived against
+    today's tree rather than the tree of the day the review ran.
+    """
+    review_folder = get_cache_base_dir() / "review"
+    if not review_folder.exists():
+        return None
+
+    newest = None
+    for cache_file in review_folder.glob("*.json"):
+        try:
+            with open(cache_file, "r", encoding="utf-8", errors="replace") as f:
+                data = json.load(f)
+        except (json.JSONDecodeError, IOError):
+            continue
+
+        if not isinstance(data, dict):
+            continue
+        if data.get("repo") != repo_name or data.get("branch") != branch_name:
+            continue
+        if data.get("action_type") not in REVIEW_ACTION_TYPES:
+            continue
+        if not (data.get("response") or {}).get("review"):
+            continue
+
+        # Timestamps are '%Y-%m-%d %H:%M:%S', so string order is date order.
+        if newest is None or data.get("datetime", "") > newest.get("datetime", ""):
+            newest = data
+
+    return newest
+
+
 def get_cached_pr_descriptions(repo_name, branch_name):
     """Searches the cache for all historically generated PRs for this repository and branch."""
     from src.i18n import __

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/src/config.py

@@ -61,6 +61,16 @@ DEFAULT_CONFIG = {
     "GITPR_RELEASE_AI_SUMMARY": "true",
     "GITPR_RELEASE_AUTO_BUMP": "true",
     "GITPR_RELEASE_PUBLISH_DRAFT_BY_DEFAULT": "true",
+    # Fix feature (gitpr fix). The excluded paths are glob patterns a patch may
+    # not touch and still count as safe; they are about *risk*, not diff noise,
+    # which is why they are not shared with the smart-excludes list.
+    "GITPR_FIX_SAFE_MAX_LINES_CHANGED": "5",
+    "GITPR_FIX_SAFE_EXCLUDED_PATHS": (
+        "database/migrations/**;**/*.ci.yml;docker/**;terraform/**;.github/workflows/**"
+    ),
+    "GITPR_FIX_REQUIRE_CONFIRMATION": "true",
+    "GITPR_FIX_CREATE_BRANCH_ON_ALL_SAFE": "true",
+    "GITPR_FIX_BRANCH_NAME_TEMPLATE": "fix/gitpr-{datetime}",
 }
 
 # Fallbacks used when the .env value is missing or not a positive number.
@@ -131,6 +141,7 @@ SKILL_FILES_BY_TYPE = {
     "issue": ".gitpr.issue.md",
     "blame": ".gitpr.blame.md",
     "release": ".gitpr.release.md",
+    "fix": ".gitpr.fix.md",
 }
 SKILL_TYPES = tuple(SKILL_FILES_BY_TYPE)
 
@@ -680,6 +691,47 @@ def get_release_settings():
     }
 
 
+def get_fix_settings():
+    """Returns the gitpr fix configuration as a flat dict.
+
+    ``safe_excluded_paths`` is the ; separated list of glob patterns a patch may
+    not touch and still be classified safe; an empty value falls back to the
+    built-in list, because clearing the field by accident must not silently drop
+    the protection. ``branch_name_template`` names the branch of a batch with
+    the vocabulary the output filenames already use ({branch} and {datetime}),
+    so there is one placeholder syntax to learn.
+    """
+    load_dotenv(ENV_FILE)
+    try:
+        max_lines = int(
+            (os.getenv("GITPR_FIX_SAFE_MAX_LINES_CHANGED") or "").strip() or 5
+        )
+        if max_lines <= 0:
+            raise ValueError
+    except ValueError:
+        max_lines = 5
+
+    # The fallback is spelled out, like every other getter here, instead of
+    # looked up in DEFAULT_CONFIG.
+    raw_paths = os.getenv("GITPR_FIX_SAFE_EXCLUDED_PATHS") or (
+        "database/migrations/**;**/*.ci.yml;docker/**;terraform/**;.github/workflows/**"
+    )
+    excluded_paths = tuple(
+        item.strip() for item in raw_paths.split(";") if item.strip()
+    )
+
+    template = (os.getenv("GITPR_FIX_BRANCH_NAME_TEMPLATE") or "").strip()
+    return {
+        "safe_max_lines_changed": max_lines,
+        "safe_excluded_paths": excluded_paths,
+        "require_confirmation": _env_bool_default_true("GITPR_FIX_REQUIRE_CONFIRMATION"),
+        "create_branch_on_all_safe": _env_bool_default_true(
+            "GITPR_FIX_CREATE_BRANCH_ON_ALL_SAFE"
+        ),
+        "branch_name_template": template or "fix/gitpr-{datetime}",
+    }
+
+
 def validate_github_token(token):
     """
     Validates a GitHub PAT by making a lightweight API call to /user.

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/src/config_schema.py

@@ -180,6 +180,12 @@ CATEGORIES = (
         __("Changelog generation and release publishing."),
         doc="release-notes.md",
     ),
+    Category(
+        "fix",
+        __("Fix"),
+        __("Review findings turned into patches, and the safety rules of a batch."),
+        doc="fix-command.md",
+    ),
     Category(
         "scm",
         __("SCM / Forge"),
@@ -221,6 +227,7 @@ SKILL_LABELS = {
     "issue": __("Issue"),
     "blame": __("Blame"),
     "release": __("Release"),
+    "fix": __("Fix"),
 }
 
 # Sub-headers shown inside a category. Generic words go through __(); forge and
@@ -614,6 +621,59 @@ FIELDS = (
         kind=KIND_TEMPLATE,
         default="{branch}_{datetime}_RELEASE.md",
     ),
+    # --------------------------------------------------------------------- Fix
+    ConfigField(
+        key="GITPR_FIX_SAFE_MAX_LINES_CHANGED",
+        label=__("Safe Patch Size"),
+        description=__(
+            "Maximum number of added plus removed lines a patch may have and still be classified as safe."
+        ),
+        category="fix",
+        kind=KIND_INT,
+        default="5",
+    ),
+    ConfigField(
+        key="GITPR_FIX_SAFE_EXCLUDED_PATHS",
+        label=__("Sensitive Paths"),
+        description=__(
+            "Semicolon separated glob patterns a patch may not touch and still be safe (migrations, workflows, containers, infrastructure)."
+        ),
+        category="fix",
+        kind=KIND_STR,
+        default=(
+            "database/migrations/**;**/*.ci.yml;docker/**;terraform/**;.github/workflows/**"
+        ),
+    ),
+    ConfigField(
+        key="GITPR_FIX_REQUIRE_CONFIRMATION",
+        label=__("Ask Before Applying"),
+        description=__(
+            "Shows the diff and asks for confirmation before a patch is written to the working tree."
+        ),
+        category="fix",
+        kind=KIND_BOOL,
+        default="true",
+    ),
+    ConfigField(
+        key="GITPR_FIX_CREATE_BRANCH_ON_ALL_SAFE",
+        label=__("Branch for a Batch"),
+        description=__(
+            "Creates a new branch when the safe patches are applied in a batch, so the current branch stays untouched."
+        ),
+        category="fix",
+        kind=KIND_BOOL,
+        default="true",
+    ),
+    ConfigField(
+        key="GITPR_FIX_BRANCH_NAME_TEMPLATE",
+        label=__("Branch Name"),
+        description=__(
+            "Name of the branch created for a batch. Placeholders: branch and datetime."
+        ),
+        category="fix",
+        kind=KIND_TEMPLATE,
+        default="fix/gitpr-{datetime}",
+    ),
     # --------------------------------------------------------------- SCM/Forge
     # The common settings stay ungrouped and always visible; the fields that
     # only exist for one forge live under its sub-header and follow the

{gitpr_cli-1.1.0 → gitpr_cli-1.2.0}/src/core.py

@@ -330,6 +330,23 @@ def _load_docs_smart_excludes():
 SMART_EXCLUDES = _load_smart_excludes() + _load_docs_smart_excludes()
 
 
+def get_smart_exclude_patterns():
+    """
+    Return the raw glob patterns behind SMART_EXCLUDES, without the prefix.
+
+    SMART_EXCLUDES is a list of git pathspecs (":(exclude)*.lock") because that
+    is what `git diff` takes on its command line. A diff fetched from a forge
+    API never passes through git, so the same exclusions have to be applied in
+    Python — this exposes the patterns both paths share, derived from the very
+    list the git command uses so the two can never drift apart.
+
+    GITPR_SKIP_SMART_EXCLUDES is honored upstream in the loaders, so an empty
+    SMART_EXCLUDES already yields an empty list here.
+    """
+    prefix = ":(exclude)"
+    return [p[len(prefix):] for p in SMART_EXCLUDES if p.startswith(prefix)]
+
+
 def _get_raw_docs_patterns():
     """
     Returns raw glob patterns for documentation extensions (e.g. ['*.md', '*.txt']).
@@ -742,8 +759,30 @@ def split_diff_into_chunks(diff_text, max_tokens=90000):
     return chunks
 
 
-def generate_pr_content(action_folder, action_type, diff_text, provider="gemini"):
-    """Sends the diff to the AI using System Instruction and returns a parsed JSON."""
+def generate_pr_content(
+    action_folder,
+    action_type,
+    diff_text,
+    provider="gemini",
+    cache_scope="",
+    store_diff=False,
+):
+    """Sends the diff to the AI using System Instruction and returns a parsed JSON.
+
+    The engine has no idea where ``diff_text`` came from and does not need one:
+    a local ``git diff`` and a pull request fetched over the API are the same
+    text by the time they arrive, so both review flows share this function.
+
+    ``cache_scope`` is appended to the cache key only — never to the prompt the
+    model receives — so a review of PR 42 and a review of an identical local
+    diff cannot answer each other. The default "" leaves the MD5 of every
+    existing local review untouched, so switching a caller to DiffSource
+    invalidates no cache.
+
+    ``store_diff`` records the reviewed diff alongside the response, which is
+    what lets ``gitpr fix`` patch against the revision that was reviewed rather
+    than the working tree of the day it runs.
+    """
     if not diff_text or not diff_text.strip():
         click.secho(
             __("⚠️ No diff found. Make some changes before running the command."),
@@ -870,7 +909,7 @@ def generate_pr_content(action_folder, action_type, diff_text, provider="gemini"
         pass  # Non-critical — never block the main flow for this metadata
 
     # TRY TO RETRIEVE FROM CACHE
-    cached_data = get_cached_response(action_folder, prompt)
+    cached_data = get_cached_response(action_folder, prompt + cache_scope)
     if cached_data:
         click.secho(__("⚡ Response retrieved from local cache."), fg="green", dim=True)
         from src.metrics import log_command_metric
@@ -1061,7 +1100,12 @@ def generate_pr_content(action_folder, action_type, diff_text, provider="gemini"
     # SAVE TO CACHE AND RETURN
     if result_json:
         save_cached_response(
-            action_folder, action_type, prompt, result_json, meta_raw=total_meta
+            action_folder,
+            action_type,
+            prompt + cache_scope,
+            result_json,
+            meta_raw=total_meta,
+            reviewed_diff=diff_text if store_diff else None,
         )
         # Fire-and-forget metric for successful AI-powered command
         from src.metrics import log_command_metric
@@ -1200,6 +1244,7 @@ def generate_skill_template():
         ".gitpr.blame.md": f"gitpr.blame{lang_suffix}.md",
         ".gitpr.issue.md": f"gitpr.issue{lang_suffix}.md",
         ".gitpr.release.md": f"gitpr.release{lang_suffix}.md",
+        ".gitpr.fix.md": f"gitpr.fix{lang_suffix}.md",
     }
 
     success_count = 0