git-graphable 0.1.0__tar.gz → 0.2.0__tar.gz

git_graphable-0.2.0/.gemini/GEMINI.md

@@ -0,0 +1,8 @@
+# Gemini Instructions
+- Always execute `just test` instead of `pytest` for running tests. Any arguments you specify will be passed through to the wrapped `pytest` command. For example, you may wish to pass `-n 0 -p no:sugar` to disable the xdist and sugar plugins.
+- Always execute `just coverage` instead of `pytest` for coverage.
+- When adding, removing, or modifying code, adhere to the code ordering guidelines in @./code-ordering.md
+- Always execute `just check` before committing any changes to ensure linting, typing, and coverage standards are met.
+- Always execute `just lint` after finishing code changes and address any issues flagged.
+- Do not use `pip` or `venv` directly; use `uv` for all environment management.
+- Do not stage or commit any changes unless explicitly instructed. When instructed to commit or push changes, you MUST first create a new feature branch and then execute `just pr <title> [body]` to prepare the pull request. If a pull request already exists for the current feature branch, push your updates to the same branch instead of creating a new pull request.

git_graphable-0.2.0/.gemini/code-ordering.md

@@ -0,0 +1,86 @@
+# Python Code Ordering Guidelines
+
+Please ensure all Python files adhere to the following structure and ordering conventions:
+
+## Module-Level Ordering
+
+The sequence of elements at the top level of a Python module should be:
+
+1.  **Module-level Docstrings:** A concise description of the file's purpose.
+    ```python
+    """
+    This module provides utility functions for path manipulation.
+    """
+    ```
+2.  **Imports:** Grouped in a specific order:
+    *   **Standard Library Imports:** (e.g., `os`, `sys`, `datetime`)
+        ```python
+        import os
+        import sys
+        from pathlib import Path
+        ```
+    *   **Third-Party Library Imports:** (e.g., `requests`, `numpy`)
+        ```python
+        import requests
+        import numpy as np
+        ```
+    *   **Local Application Imports:** Imports from your project's own modules.
+        ```python
+        from . import utils
+        from ..core import models
+        ```
+3.  **Module-level Globals/Constants:** Variables declared at the module level, typically in `ALL_CAPS`.
+    ```python
+    DEFAULT_TIMEOUT = 30
+    CONFIG_PATH = "/etc/myapp/config.ini"
+    ```
+4.  **Classes and Functions:**
+    *   Higher-level definitions should usually precede lower-level helper functions or classes.
+    *   For classes, follow the "Class Internal Ordering" below.
+    *   For functions, utility functions often come before main operational functions.
+5.  **Main Entry Point:** The `if __name__ == "__main__":` block, placed at the very bottom.
+
+## Class Internal Ordering
+
+Within a class, elements should be ordered logically and by visibility:
+
+1.  **Class Attributes:** Constants or shared state variables belonging to the class.
+    ```python
+    class MyClass:
+        CLASS_CONSTANT = 100
+    ```
+2.  **`__init__` Method:** The constructor.
+    ```python
+    def __init__(self, value):
+        self.value = value
+    ```
+3.  **Magic Methods:** Other dunder methods (e.g., `__str__`, `__repr__`, `__eq__`).
+    ```python
+    def __str__(self):
+        return f"MyClass({self.value})"
+    ```
+4.  **Public Methods:** The primary ways other code interacts with your class.
+    ```python
+    def public_method(self):
+        # ...
+    ```
+5.  **Protected and Private Methods:** Implementation details prefixed with `_` or `__` (that aren't magic methods).
+    ```python
+    def _helper_method(self):
+        # ...
+    ```
+6.  **Static and Class Methods:** Often placed at the end, or grouped near related public methods if they act as factory methods.
+    ```python
+    @staticmethod
+    def static_method():
+        # ...
+
+    @classmethod
+    def class_method(cls):
+        # ...
+    ```
+
+## General Layout Principles
+
+*   **Vertical Distance:** Keep related methods close together. Use two blank lines between top-level definitions (module docstring, imports, classes, functions) and one blank line between methods within a class.
+*   **Step-Down Rule:** Place a "caller" method immediately above the "callee" method it uses. (This is more of a guideline for readability than a strict ordering rule.)

git_graphable-0.2.0/.github/dependabot.yml

@@ -0,0 +1,23 @@
+version: 2
+updates:
+  # Maintain dependencies for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    groups:
+      actions:
+        patterns:
+          - "*"
+
+  # Maintain Python dependencies
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Since we use uv, Dependabot will look at pyproject.toml
+    open-pull-requests-limit: 5
+    groups:
+      dependencies:
+        patterns:
+          - "*"

{git_graphable-0.1.0 → git_graphable-0.2.0}/.github/workflows/ci.yml

@@ -6,15 +6,20 @@ on:
   pull_request:
     branches: [ main ]
 
+# Grant minimal permissions by default
+permissions:
+  contents: read
+
 jobs:
   check:
     name: Check and Test
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - name: Checkout repository
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v5
+        uses: astral-sh/setup-uv@5a095e7a2014a4212f075830d4f7277575a9d098 # v7.3.1
         with:
           enable-cache: true
 
@@ -22,7 +27,7 @@ jobs:
         run: uv python install 3.13
 
       - name: Install just
-        uses: extractions/setup-just@v2
+        uses: extractions/setup-just@f8a3cce218d9f83db3a2ecd90e41ac3de6cdfd9b # v3.1.0
 
       - name: Run checks
         run: just check

{git_graphable-0.1.0 → git_graphable-0.2.0}/.github/workflows/publish.yml

@@ -13,10 +13,11 @@ jobs:
       id-token: write  # Mandatory for trusted publishing
       contents: read
     steps:
-      - uses: actions/checkout@v4
+      - name: Checkout repository
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v5
+        uses: astral-sh/setup-uv@5a095e7a2014a4212f075830d4f7277575a9d098 # v7.3.1
         with:
           enable-cache: true
 

{git_graphable-0.1.0 → git_graphable-0.2.0}/.gitignore

@@ -129,3 +129,10 @@ cython_debug/
 
 # OS X
 .DS_Store
+
+# Examples
+examples/repos/
+examples/assets/
+
+# Temporary test assets
+test_pr.mmd

{git_graphable-0.1.0 → git_graphable-0.2.0}/Justfile

@@ -1,7 +1,7 @@
 set dotenv-load
 
-GIT_BRANCH:=`git branch --show-current`
-GIT_COMMIT:=`git rev-parse HEAD`
+GIT_BRANCH:=`git branch --show-current | xargs echo -n | grep . || echo "unknown"`
+GIT_COMMIT:=`git rev-parse HEAD | xargs echo -n | grep . || echo "unknown"`
 
 @_:
     just --list
@@ -58,6 +58,7 @@ publish: build
 
 [group('qa')]
 check: lint typing coverage
+    uv run git-graphable . --check --min-score 80 --bare --highlight-wip --highlight-direct-pushes
 
 [group('qa')]
 @coverage *args:
@@ -87,6 +88,27 @@ testrep:
 typing:
     uv run ty check
 
+[group('run')]
+pr title body="":
+    #!/usr/bin/env bash
+    CURRENT_BRANCH=$(git branch --show-current)
+    if [ "$CURRENT_BRANCH" == "main" ]; then
+        echo "Error: You are on the 'main' branch. Please create a feature branch first!"
+        exit 1
+    fi
+    just check
+    git push -u origin "$CURRENT_BRANCH"
+    gh pr create --repo TheTrueSCU/git-graphable --head "$CURRENT_BRANCH" --title "{{ title }}" --body "{{ body }}"
+
 [group('run')]
 @run *args:
     uv run git-graphable {{ args }}
+
+[group('demo')]
+generate-examples:
+    uv run python examples/generate_demos.py
+    uv run git-graphable examples/repos/repo-pristine --engine mermaid -o examples/assets/pristine.mmd --highlight-critical --critical-branch main --highlight-authors --bare
+    uv run git-graphable examples/repos/repo-messy --engine mermaid -o examples/assets/messy.mmd --highlight-wip --highlight-direct-pushes --highlight-stale --bare
+    uv run git-graphable examples/repos/repo-features --engine mermaid -o examples/assets/features.mmd --highlight-orphans --highlight-diverging-from main --bare
+    uv run git-graphable examples/repos/repo-risk-silo --engine mermaid -o examples/assets/silo.mmd --highlight-silos --silo-threshold 20 --bare
+    uv run git-graphable examples/repos/repo-complex-hygiene --engine mermaid -o examples/assets/complex.mmd --highlight-back-merges --bare

git_graphable-0.2.0/PKG-INFO

@@ -0,0 +1,166 @@
+Metadata-Version: 2.4
+Name: git-graphable
+Version: 0.2.0
+Summary: A powerful Git history visualizer and hygiene linter with CI gating.
+Project-URL: Homepage, https://github.com/TheTrueSCU/git-graphable
+Project-URL: Issues, https://github.com/TheTrueSCU/git-graphable/issues
+Project-URL: Repository, https://github.com/TheTrueSCU/git-graphable
+Author-email: Richard West <dopplereffect.us@gmail.com>
+Keywords: analysis,ci,d2,git,git-flow,github,graph,hygiene,lint,mermaid,topology,visualization
+Requires-Python: >=3.13
+Requires-Dist: graphable>=0.6.0
+Provides-Extra: cli
+Requires-Dist: rich>=13.0.0; extra == 'cli'
+Requires-Dist: typer>=0.12.0; extra == 'cli'
+Description-Content-Type: text/markdown
+
+# Git Graphable
+
+A powerful Python tool to convert Git commit history into beautiful, interactive flowcharts using the `graphable` library. Supporting Mermaid, D2, Graphviz, and PlantUML.
+
+## Git Plugin Support
+When installed in your PATH, you can use this as a native Git plugin:
+```bash
+git graphable .
+```
+
+## Features
+
+- **Multi-Engine Support**: Export to Mermaid (.mmd), D2 (.d2), Graphviz (.dot), or PlantUML (.puml).
+- **Automatic Visualization**: Generates and opens an image (SVG/PNG) automatically if no output is specified.
+- **Advanced Highlighting**: Visualize author patterns, topological distance, and specific merge paths.
+- **GitHub Integration**: Highlight commits based on pull request status (Merged, Open, Closed, Draft) using the `gh` CLI.
+- **Hygiene Analysis**: Automatically detect WIP commits, direct pushes to protected branches, squashed PRs, back-merges, and contributor silos.
+- **Health Scoring**: Get a numeric "Hygiene Score" (0-100%) with a color-coded grade and detailed breakdown of workflow anti-patterns.
+- **CI Gating**: Use the `--check` flag to return a non-zero exit code if the hygiene score falls below a threshold (configurable via `--min-score`).
+- **Flexible Input**: Works with local repository paths or remote Git URLs.
+- **Dual CLI**: Modern Rich/Typer interface with a robust argparse fallback for bare environments.
+
+## Installation
+
+```bash
+# Using uv (recommended)
+uv sync --all-extras
+```
+
+## Usage
+
+For a complete reference of all command-line options, see the [USAGE.md](USAGE.md) file. For visual demonstrations of all features, see [examples/EXAMPLES.md](examples/EXAMPLES.md).
+
+```bash
+# Basic usage (opens a Mermaid image)
+uv run git-graphable .
+
+# Highlight PR status (requires gh CLI)
+uv run git-graphable . --highlight-pr-status
+
+# Specify an engine and output file
+uv run git-graphable https://github.com/TheTrueSCU/graphable/ --engine d2 -o graph.svg
+
+# Simplify the graph (only show branches/tags)
+uv run git-graphable . --simplify
+```
+
+## Highlighting Options
+
+Git Graphable provides several ways to highlight commits and relationships. Multiple options can be combined to layer information.
+
+| Option | Target | Effect | Conflicts With |
+| :--- | :--- | :--- | :--- |
+| `--highlight-authors` | **Fill** | Unique color per author | PR Status, Distance, Stale, WIP |
+| `--highlight-pr-status` | **Fill/Stroke**| Color by PR state (Merged=Purple, Open=Green) | Authors, Distance, Stale, WIP |
+| `--highlight-distance-from` | **Fill** | Blue gradient fading by distance | Authors, PR Status, Stale, WIP |
+| `--highlight-stale` | **Fill** | Gradient white to red by age | Authors, PR Status, Distance, WIP |
+| `--highlight-wip` | **Fill** | Yellow fill for WIP/TODO commits | Authors, PR Status, Distance, Stale |
+| `--highlight-path` | **Edge** | Thick Orange edge connecting nodes | None |
+| `--highlight-critical` | **Stroke** | Thick Red Solid outline | None |
+| `--highlight-diverging-from` | **Stroke** | Orange Dashed outline | None |
+| `--highlight-orphans` | **Stroke** | Grey Dashed outline | None |
+| `--highlight-long-running` | **Stroke/Edge** | Purple outline and thick Purple edge | None |
+| `--highlight-direct-pushes` | **Stroke** | Thick Red Dashed outline | None |
+| `--highlight-squashed` | **Stroke/Edge** | Grey Solid outline and dashed Grey logical merge edge | None |
+| `--highlight-back-merges` | **Stroke** | Orange Dashed outline | None |
+| `--highlight-silos` | **Stroke** | Blue Solid outline | None |
+
+### Highlighting Priorities
+- **Fill**: `--highlight-authors`, `--highlight-pr-status`, `--highlight-distance-from`, `--highlight-stale`, and `--highlight-wip` are mutually exclusive.
+- **Edge**: Path highlighting (Thick Orange) takes priority over Long-Running highlighting (Thick Purple), which takes priority over Logical Squashed Merges (Dashed Grey).
+- **Stroke**: Critical outlines (Thick Red Solid) take priority over Direct Pushes (Thick Red Dashed), which take priority over PR Conflicts (Thick Red Solid), which take priority over Back-Merges (Orange Dashed), which take priority over Squash Commits (Grey Solid), which take priority over Contributor Silos (Blue Solid), which take priority over all other outlines (Divergence, Orphan, Long-Running).
+
+## Advanced Examples
+
+### Hygiene Analysis
+Identify problematic patterns like direct pushes to `main`, messy WIP commits, back-merges from `main`, or contributor silos:
+```bash
+uv run git-graphable . --highlight-direct-pushes --highlight-wip --highlight-squashed --highlight-back-merges --highlight-silos
+```
+
+### PR Status Highlighting
+View the current state of all PRs in your repository graph:
+```bash
+uv run git-graphable . --highlight-pr-status
+```
+
+### Divergence Analysis (Hygiene)
+Highlight commits that exist in `main` but are missing from your feature branches:
+```bash
+uv run git-graphable . --highlight-diverging-from main
+```
+
+### Large Repositories
+For repositories with long histories, use the `--limit` flag to keep the graph readable and avoid engine rendering limits:
+```bash
+uv run git-graphable . --limit 100 --highlight-authors
+```
+
+## Configuration
+
+Git Graphable can be configured via a TOML file (`.git-graphable.toml` or `pyproject.toml`). CLI flags always take precedence over configuration file settings.
+
+### Configuration Locations
+The tool searches for configuration in the following order:
+1. File specified via `--config <path>`
+2. `.git-graphable.toml` in the repository root
+3. `pyproject.toml` in the repository root (under `[tool.git-graphable]`)
+
+### Example `.git-graphable.toml`
+```toml
+[git-graphable]
+production_branch = "main"
+development_branch = "develop"
+simplify = true
+limit = 100
+date_format = "%Y-%m-%d"
+highlight_critical = true
+critical_branches = ["main", "prod"]
+highlight_pr_status = true
+highlight_wip = true
+wip_keywords = ["wip", "todo", "fixme", "temp"]
+highlight_direct_pushes = true
+highlight_squashed = true
+highlight_back_merges = true
+highlight_silos = true
+silo_commit_threshold = 20
+silo_author_count = 1
+min_hygiene_score = 80
+```
+
+### Example `pyproject.toml`
+```toml
+[tool.git-graphable]
+development_branch = "main"
+simplify = true
+highlight_authors = true
+```
+
+## Development
+
+Run tests and linting:
+```bash
+just check
+```
+
+### CI/CD
+This project uses GitHub Actions for continuous integration and automated publishing:
+- **CI**: Runs `just check` on all pushes and PRs to `main`.
+- **Publish**: Automatically builds and publishes to PyPI when a version tag (`v*`) is pushed.

git_graphable-0.2.0/README.md

@@ -0,0 +1,150 @@
+# Git Graphable
+
+A powerful Python tool to convert Git commit history into beautiful, interactive flowcharts using the `graphable` library. Supporting Mermaid, D2, Graphviz, and PlantUML.
+
+## Git Plugin Support
+When installed in your PATH, you can use this as a native Git plugin:
+```bash
+git graphable .
+```
+
+## Features
+
+- **Multi-Engine Support**: Export to Mermaid (.mmd), D2 (.d2), Graphviz (.dot), or PlantUML (.puml).
+- **Automatic Visualization**: Generates and opens an image (SVG/PNG) automatically if no output is specified.
+- **Advanced Highlighting**: Visualize author patterns, topological distance, and specific merge paths.
+- **GitHub Integration**: Highlight commits based on pull request status (Merged, Open, Closed, Draft) using the `gh` CLI.
+- **Hygiene Analysis**: Automatically detect WIP commits, direct pushes to protected branches, squashed PRs, back-merges, and contributor silos.
+- **Health Scoring**: Get a numeric "Hygiene Score" (0-100%) with a color-coded grade and detailed breakdown of workflow anti-patterns.
+- **CI Gating**: Use the `--check` flag to return a non-zero exit code if the hygiene score falls below a threshold (configurable via `--min-score`).
+- **Flexible Input**: Works with local repository paths or remote Git URLs.
+- **Dual CLI**: Modern Rich/Typer interface with a robust argparse fallback for bare environments.
+
+## Installation
+
+```bash
+# Using uv (recommended)
+uv sync --all-extras
+```
+
+## Usage
+
+For a complete reference of all command-line options, see the [USAGE.md](USAGE.md) file. For visual demonstrations of all features, see [examples/EXAMPLES.md](examples/EXAMPLES.md).
+
+```bash
+# Basic usage (opens a Mermaid image)
+uv run git-graphable .
+
+# Highlight PR status (requires gh CLI)
+uv run git-graphable . --highlight-pr-status
+
+# Specify an engine and output file
+uv run git-graphable https://github.com/TheTrueSCU/graphable/ --engine d2 -o graph.svg
+
+# Simplify the graph (only show branches/tags)
+uv run git-graphable . --simplify
+```
+
+## Highlighting Options
+
+Git Graphable provides several ways to highlight commits and relationships. Multiple options can be combined to layer information.
+
+| Option | Target | Effect | Conflicts With |
+| :--- | :--- | :--- | :--- |
+| `--highlight-authors` | **Fill** | Unique color per author | PR Status, Distance, Stale, WIP |
+| `--highlight-pr-status` | **Fill/Stroke**| Color by PR state (Merged=Purple, Open=Green) | Authors, Distance, Stale, WIP |
+| `--highlight-distance-from` | **Fill** | Blue gradient fading by distance | Authors, PR Status, Stale, WIP |
+| `--highlight-stale` | **Fill** | Gradient white to red by age | Authors, PR Status, Distance, WIP |
+| `--highlight-wip` | **Fill** | Yellow fill for WIP/TODO commits | Authors, PR Status, Distance, Stale |
+| `--highlight-path` | **Edge** | Thick Orange edge connecting nodes | None |
+| `--highlight-critical` | **Stroke** | Thick Red Solid outline | None |
+| `--highlight-diverging-from` | **Stroke** | Orange Dashed outline | None |
+| `--highlight-orphans` | **Stroke** | Grey Dashed outline | None |
+| `--highlight-long-running` | **Stroke/Edge** | Purple outline and thick Purple edge | None |
+| `--highlight-direct-pushes` | **Stroke** | Thick Red Dashed outline | None |
+| `--highlight-squashed` | **Stroke/Edge** | Grey Solid outline and dashed Grey logical merge edge | None |
+| `--highlight-back-merges` | **Stroke** | Orange Dashed outline | None |
+| `--highlight-silos` | **Stroke** | Blue Solid outline | None |
+
+### Highlighting Priorities
+- **Fill**: `--highlight-authors`, `--highlight-pr-status`, `--highlight-distance-from`, `--highlight-stale`, and `--highlight-wip` are mutually exclusive.
+- **Edge**: Path highlighting (Thick Orange) takes priority over Long-Running highlighting (Thick Purple), which takes priority over Logical Squashed Merges (Dashed Grey).
+- **Stroke**: Critical outlines (Thick Red Solid) take priority over Direct Pushes (Thick Red Dashed), which take priority over PR Conflicts (Thick Red Solid), which take priority over Back-Merges (Orange Dashed), which take priority over Squash Commits (Grey Solid), which take priority over Contributor Silos (Blue Solid), which take priority over all other outlines (Divergence, Orphan, Long-Running).
+
+## Advanced Examples
+
+### Hygiene Analysis
+Identify problematic patterns like direct pushes to `main`, messy WIP commits, back-merges from `main`, or contributor silos:
+```bash
+uv run git-graphable . --highlight-direct-pushes --highlight-wip --highlight-squashed --highlight-back-merges --highlight-silos
+```
+
+### PR Status Highlighting
+View the current state of all PRs in your repository graph:
+```bash
+uv run git-graphable . --highlight-pr-status
+```
+
+### Divergence Analysis (Hygiene)
+Highlight commits that exist in `main` but are missing from your feature branches:
+```bash
+uv run git-graphable . --highlight-diverging-from main
+```
+
+### Large Repositories
+For repositories with long histories, use the `--limit` flag to keep the graph readable and avoid engine rendering limits:
+```bash
+uv run git-graphable . --limit 100 --highlight-authors
+```
+
+## Configuration
+
+Git Graphable can be configured via a TOML file (`.git-graphable.toml` or `pyproject.toml`). CLI flags always take precedence over configuration file settings.
+
+### Configuration Locations
+The tool searches for configuration in the following order:
+1. File specified via `--config <path>`
+2. `.git-graphable.toml` in the repository root
+3. `pyproject.toml` in the repository root (under `[tool.git-graphable]`)
+
+### Example `.git-graphable.toml`
+```toml
+[git-graphable]
+production_branch = "main"
+development_branch = "develop"
+simplify = true
+limit = 100
+date_format = "%Y-%m-%d"
+highlight_critical = true
+critical_branches = ["main", "prod"]
+highlight_pr_status = true
+highlight_wip = true
+wip_keywords = ["wip", "todo", "fixme", "temp"]
+highlight_direct_pushes = true
+highlight_squashed = true
+highlight_back_merges = true
+highlight_silos = true
+silo_commit_threshold = 20
+silo_author_count = 1
+min_hygiene_score = 80
+```
+
+### Example `pyproject.toml`
+```toml
+[tool.git-graphable]
+development_branch = "main"
+simplify = true
+highlight_authors = true
+```
+
+## Development
+
+Run tests and linting:
+```bash
+just check
+```
+
+### CI/CD
+This project uses GitHub Actions for continuous integration and automated publishing:
+- **CI**: Runs `just check` on all pushes and PRs to `main`.
+- **Publish**: Automatically builds and publishes to PyPI when a version tag (`v*`) is pushed.

git_graphable-0.2.0/SECURITY.md

@@ -0,0 +1,14 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+We take the security of this project seriously. If you believe you have found a security vulnerability, please do not report it via a public issue. Instead, please report it through GitHub's private vulnerability reporting feature or contact the maintainer directly at [dopplereffect.us@gmail.com].
+
+## Supported Versions
+
+Only the latest version of `git-graphable` is currently supported for security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 0.1.x   | :white_check_mark: |
+| < 0.1.0 | :x:                |

git_graphable-0.2.0/USAGE.md

@@ -0,0 +1,52 @@
+# `git-graphable`
+
+Git graph to Mermaid/Graphviz/D2/PlantUML converter.
+
+**Usage**:
+
+```console
+$ git-graphable [OPTIONS] PATH
+```
+
+**Arguments**:
+
+* `PATH`: Path to local directory or git URL  [required]
+
+**Options**:
+
+* `--config TEXT`: Path to TOML configuration file
+* `--production-branch TEXT`: Production branch name (e.g. main, master)
+* `--development-branch TEXT`: Development branch name (e.g. develop, main)
+* `--date-format TEXT`: Date format for commit labels  [default: %Y%m%d%H%M%S]
+* `--engine [mermaid|graphviz|d2|plantuml]`: Visualization engine  [default: mermaid]
+* `-o, --output TEXT`: Output file path
+* `--image`: Export as image even when output path is provided
+* `--simplify`: Pass --simplify-by-decoration to git log
+* `--limit INTEGER`: Limit the number of commits to process
+* `--highlight-critical`: Highlight critical branches
+* `--critical-branch TEXT`: Branch name to treat as critical
+* `--highlight-authors`: Assign colors to different authors
+* `--highlight-distance-from TEXT`: Base branch/hash for distance highlighting
+* `--highlight-path TEXT`: Highlight path between two SHAs (START..END)
+* `--highlight-diverging-from TEXT`: Base branch/hash for divergence/behind analysis
+* `--highlight-orphans`: Highlight dangling/orphan commits
+* `--highlight-stale`: Highlight stale branch tips
+* `--stale-days INTEGER`: Threshold in days for stale branches
+* `--highlight-long-running`: Highlight long-running branches
+* `--long-running-days INTEGER`: Threshold in days for long-running branches
+* `--long-running-base TEXT`: Base branch for long-running analysis
+* `--highlight-pr-status`: Highlight commits based on GitHub PR status
+* `--highlight-wip`: Highlight WIP/TODO commits
+* `--wip-keyword TEXT`: Additional keyword to trigger WIP highlighting
+* `--highlight-direct-pushes`: Highlight non-merge commits on protected branches
+* `--highlight-squashed`: Highlight squashed PRs and logically link them
+* `--highlight-back-merges`: Highlight redundant back-merges from base branch
+* `--highlight-silos`: Highlight branches dominated by too few authors
+* `--silo-threshold INTEGER`: Commit count threshold for silo detection
+* `--silo-author-count INTEGER`: Author count threshold for silo detection
+* `--check`: Exit with non-zero if hygiene score is below threshold
+* `--min-score INTEGER`: Minimum hygiene score required for --check
+* `--bare`: Force bare mode (no rich output)
+* `--install-completion`: Install completion for the current shell.
+* `--show-completion`: Show completion for the current shell, to copy it or customize the installation.
+* `--help`: Show this message and exit.