gitpr-cli 0.0.34__tar.gz → 0.0.35__tar.gz

{gitpr_cli-0.0.34 → gitpr_cli-0.0.35}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gitpr-cli
-Version: 0.0.34
+Version: 0.0.35
 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
@@ -173,7 +173,7 @@ You can pass the following *flags* for specific actions:
   * **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.
   * **Archaeological/Technical Debt Issue (`gitpr -is -b file:lines`):** Reads the timeline of a specific business rule. **Why use:** Ideal for documenting technical debt, explaining how a legacy code block evolved and why it needs to be refactored.
-	* **PR Publisher (default):** Running `gitpr` generates the PR description with AI, saves the `.md` file to `.gitpr/reports/pr_desc/`, and opens an interactive terminal interface (TUI) to review, edit, and publish the Pull Request directly to GitHub via REST API. Before generation, it checks for unstaged files and offers a modal to manage them. Use `--no-publish` to save only the PR file locally without opening the publisher, or `--no-edit` to auto-commit pending changes (with lint validation), auto-push, and publish immediately — handling existing PR updates and optional auto-merge. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md)
+	* **PR Publisher (default):** Running `gitpr` generates the PR description with AI, saves the `.md` file to `.gitpr/reports/pr_desc/`, and opens an interactive terminal interface (TUI) to review, edit, and publish the Pull Request directly to GitHub via REST API. Before generation, it checks for unstaged files and offers a modal to manage them. Use `--no-publish` to save only the PR file locally without opening the publisher, or `--no-edit` to auto-commit pending changes (with lint validation), auto-push, and publish immediately — handling existing PR updates, optional auto-merge, and clear error feedback when merge conflicts occur. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md)
 * `-h` or `--help`: Shows the general help with all options. Use together with another flag for **contextual help** (e.g.: `gitpr -h --issue`, `gitpr -h --linter`) with a direct link to the detailed documentation of each feature.
 * `-u` or `--update`: Checks and installs the latest version of GitPR (Auto-Updater).
 
@@ -322,6 +322,25 @@ Once configured, use natural language in your editor's AI chat:
 | `run_linter` | Static linter against `.gitpr.linter.yml` |
 | `analyze_blame` | Git blame + AI classification |
 | `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) |
+
+### Direct CLI Invocation
+
+All GitPR MCP tools can be invoked directly from the terminal without starting the stdio server:
+
+```bash
+# List all available tools with their parameter signatures
+gitpr-mcp --tool
+
+# Invoke a specific tool
+gitpr-mcp --tool get_git_context
+gitpr-mcp --tool review_code
+gitpr-mcp --tool generate_commit_message --tool-args '{"diff_text":"..."}'
+gitpr-mcp --tool analyze_blame --tool-args '{"file_path":"src/main.py","start_line":"270","end_line":"284"}'
+```
+
+This is useful for scripting, CI/CD pipelines, and one-off queries where you don't need a persistent MCP server. JSON output goes to stdout; all diagnostic messages go to stderr — safe for piping.
 
 📖 **Full documentation:** [docs/mcp-integration.md](https://github.com/natanfiuza/gitpr/blob/main/docs/mcp-integration.md) — available in 5 languages (EN, PT-BR, PT-PT, ES, FR).
 

{gitpr_cli-0.0.34 → gitpr_cli-0.0.35}/README.md

@@ -154,7 +154,7 @@ You can pass the following *flags* for specific actions:
   * **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.
   * **Archaeological/Technical Debt Issue (`gitpr -is -b file:lines`):** Reads the timeline of a specific business rule. **Why use:** Ideal for documenting technical debt, explaining how a legacy code block evolved and why it needs to be refactored.
-	* **PR Publisher (default):** Running `gitpr` generates the PR description with AI, saves the `.md` file to `.gitpr/reports/pr_desc/`, and opens an interactive terminal interface (TUI) to review, edit, and publish the Pull Request directly to GitHub via REST API. Before generation, it checks for unstaged files and offers a modal to manage them. Use `--no-publish` to save only the PR file locally without opening the publisher, or `--no-edit` to auto-commit pending changes (with lint validation), auto-push, and publish immediately — handling existing PR updates and optional auto-merge. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md)
+	* **PR Publisher (default):** Running `gitpr` generates the PR description with AI, saves the `.md` file to `.gitpr/reports/pr_desc/`, and opens an interactive terminal interface (TUI) to review, edit, and publish the Pull Request directly to GitHub via REST API. Before generation, it checks for unstaged files and offers a modal to manage them. Use `--no-publish` to save only the PR file locally without opening the publisher, or `--no-edit` to auto-commit pending changes (with lint validation), auto-push, and publish immediately — handling existing PR updates, optional auto-merge, and clear error feedback when merge conflicts occur. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md)
 * `-h` or `--help`: Shows the general help with all options. Use together with another flag for **contextual help** (e.g.: `gitpr -h --issue`, `gitpr -h --linter`) with a direct link to the detailed documentation of each feature.
 * `-u` or `--update`: Checks and installs the latest version of GitPR (Auto-Updater).
 
@@ -303,6 +303,25 @@ Once configured, use natural language in your editor's AI chat:
 | `run_linter` | Static linter against `.gitpr.linter.yml` |
 | `analyze_blame` | Git blame + AI classification |
 | `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) |
+
+### Direct CLI Invocation
+
+All GitPR MCP tools can be invoked directly from the terminal without starting the stdio server:
+
+```bash
+# List all available tools with their parameter signatures
+gitpr-mcp --tool
+
+# Invoke a specific tool
+gitpr-mcp --tool get_git_context
+gitpr-mcp --tool review_code
+gitpr-mcp --tool generate_commit_message --tool-args '{"diff_text":"..."}'
+gitpr-mcp --tool analyze_blame --tool-args '{"file_path":"src/main.py","start_line":"270","end_line":"284"}'
+```
+
+This is useful for scripting, CI/CD pipelines, and one-off queries where you don't need a persistent MCP server. JSON output goes to stdout; all diagnostic messages go to stderr — safe for piping.
 
 📖 **Full documentation:** [docs/mcp-integration.md](https://github.com/natanfiuza/gitpr/blob/main/docs/mcp-integration.md) — available in 5 languages (EN, PT-BR, PT-PT, ES, FR).
 

{gitpr_cli-0.0.34 → gitpr_cli-0.0.35}/gitpr_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gitpr-cli
-Version: 0.0.34
+Version: 0.0.35
 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
@@ -173,7 +173,7 @@ You can pass the following *flags* for specific actions:
   * **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.
   * **Archaeological/Technical Debt Issue (`gitpr -is -b file:lines`):** Reads the timeline of a specific business rule. **Why use:** Ideal for documenting technical debt, explaining how a legacy code block evolved and why it needs to be refactored.
-	* **PR Publisher (default):** Running `gitpr` generates the PR description with AI, saves the `.md` file to `.gitpr/reports/pr_desc/`, and opens an interactive terminal interface (TUI) to review, edit, and publish the Pull Request directly to GitHub via REST API. Before generation, it checks for unstaged files and offers a modal to manage them. Use `--no-publish` to save only the PR file locally without opening the publisher, or `--no-edit` to auto-commit pending changes (with lint validation), auto-push, and publish immediately — handling existing PR updates and optional auto-merge. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md)
+	* **PR Publisher (default):** Running `gitpr` generates the PR description with AI, saves the `.md` file to `.gitpr/reports/pr_desc/`, and opens an interactive terminal interface (TUI) to review, edit, and publish the Pull Request directly to GitHub via REST API. Before generation, it checks for unstaged files and offers a modal to manage them. Use `--no-publish` to save only the PR file locally without opening the publisher, or `--no-edit` to auto-commit pending changes (with lint validation), auto-push, and publish immediately — handling existing PR updates, optional auto-merge, and clear error feedback when merge conflicts occur. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md)
 * `-h` or `--help`: Shows the general help with all options. Use together with another flag for **contextual help** (e.g.: `gitpr -h --issue`, `gitpr -h --linter`) with a direct link to the detailed documentation of each feature.
 * `-u` or `--update`: Checks and installs the latest version of GitPR (Auto-Updater).
 
@@ -322,6 +322,25 @@ Once configured, use natural language in your editor's AI chat:
 | `run_linter` | Static linter against `.gitpr.linter.yml` |
 | `analyze_blame` | Git blame + AI classification |
 | `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) |
+
+### Direct CLI Invocation
+
+All GitPR MCP tools can be invoked directly from the terminal without starting the stdio server:
+
+```bash
+# List all available tools with their parameter signatures
+gitpr-mcp --tool
+
+# Invoke a specific tool
+gitpr-mcp --tool get_git_context
+gitpr-mcp --tool review_code
+gitpr-mcp --tool generate_commit_message --tool-args '{"diff_text":"..."}'
+gitpr-mcp --tool analyze_blame --tool-args '{"file_path":"src/main.py","start_line":"270","end_line":"284"}'
+```
+
+This is useful for scripting, CI/CD pipelines, and one-off queries where you don't need a persistent MCP server. JSON output goes to stdout; all diagnostic messages go to stderr — safe for piping.
 
 📖 **Full documentation:** [docs/mcp-integration.md](https://github.com/natanfiuza/gitpr/blob/main/docs/mcp-integration.md) — available in 5 languages (EN, PT-BR, PT-PT, ES, FR).
 

{gitpr_cli-0.0.34 → gitpr_cli-0.0.35}/src/core.py

@@ -333,10 +333,10 @@ def get_changed_docs_list(ancestor_hash=None):
             check=True,
         )
 
-        all_files = result.stdout.strip().split("\n")
+        all_files = result.stdout.splitlines()
         doc_files = []
         for f in all_files:
-            if not f:
+            if not f.strip():
                 continue
             for pattern in raw_patterns:
                 if fnmatch.fnmatch(f, pattern):
@@ -1153,8 +1153,8 @@ def get_uncommitted_summary():
             capture_output=True, text=True, encoding="utf-8", errors="replace",
         )
         summary = {"staged": [], "unstaged": [], "untracked": []}
-        for line in result.stdout.strip().split("\n"):
-            if not line:
+        for line in result.stdout.splitlines():
+            if not line.strip():
                 continue
             x, y = line[0], line[1]
             path = line[3:].strip()
@@ -1183,8 +1183,8 @@ def get_unstaged_files():
             capture_output=True, text=True, encoding="utf-8", errors="replace",
         )
         files = []
-        for line in result.stdout.strip().split("\n"):
-            if not line:
+        for line in result.stdout.splitlines():
+            if not line.strip():
                 continue
             status_x = line[0] if len(line) > 0 else ""
             status_y = line[1] if len(line) > 1 else ""

{gitpr_cli-0.0.34 → gitpr_cli-0.0.35}/src/main.py

@@ -953,10 +953,10 @@ def cli(commit, review, fullreview, linter, skill, update, installhooks, install
             continue
 
         if app.final_message:
-            cor = "green" if app.final_action in ["saved", "created"] else "red"
+            cor = "green" if app.final_action in ["saved", "created", "merged"] else "red"
             click.secho(f"\n{app.final_message}\n", fg=cor, bold=True)
 
-        if app.final_action == "created" and app.final_pr_url:
+        if app.final_action in ["created", "merged", "merge_failed"] and app.final_pr_url:
             if click.confirm(__("🔗 Open the Pull Request in your browser?")):
                 import webbrowser
                 webbrowser.open(app.final_pr_url)