Rename CLI tool from 'chel' to 'kelo' and update related documentation

Author: MrBearing

.github/workflows/publish-report.yml

@@ -62,7 +62,7 @@ jobs:
       - name: Generate ROS1 analysis JSON
         run: |
           cd moveit
-          chel analyze --platform ros1 -f json -o ../analysis-ros1.json .
+          kelo analyze --platform ros1 -f json -o ../analysis-ros1.json .
 
       - name: Copy ROS1 analysis JSON into site output
         run: |
@@ -71,7 +71,7 @@ jobs:
 
       - name: Generate ROS1 HTML report
         run: |
-          chel report analysis-ros1.json -o report_output/ros1/ --config chelonian/docs/github_pages_report.toml
+          kelo report analysis-ros1.json -o report_output/ros1/ --config chelonian/docs/github_pages_report.toml
 
       - name: Checkout sample ROS2 workspace (moveit2)
         uses: actions/checkout@v4
@@ -83,7 +83,7 @@ jobs:
       - name: Generate ROS2 analysis JSON
         run: |
           cd moveit2
-          chel analyze --platform ros2 -f json -o ../analysis-ros2.json .
+          kelo analyze --platform ros2 -f json -o ../analysis-ros2.json .
 
       - name: Copy ROS2 analysis JSON into site output
         run: |
@@ -92,7 +92,7 @@ jobs:
 
       - name: Generate ROS2 HTML report
         run: |
-          chel report analysis-ros2.json -o report_output/ros2/ --config chelonian/docs/github_pages_report_ros2.toml
+          kelo report analysis-ros2.json -o report_output/ros2/ --config chelonian/docs/github_pages_report_ros2.toml
 
       - name: Copy portal index.html
         run: |

Cargo.toml

@@ -11,7 +11,7 @@ keywords = ["ros", "ros2", "static-analysis", "migration", "robotics"]
 categories = ["development-tools", "command-line-utilities"]
 
 [[bin]]
-name = "chel"
+name = "kelo"
 path = "src/main.rs"
 
 [dependencies]

README.md

@@ -19,61 +19,61 @@ Install (from source):
 cargo install --path . --locked
 ```
 
-After installation use `chel` from your PATH.
+After installation use `kelo` from your PATH.
 
 Analyze a workspace (text output):
 
 ```bash
-chel analyze /path/to/ros/workspace
+kelo analyze /path/to/ros/workspace
 ```
 
 Select a platform (load platform-specific builtin rules):
 
 ```bash
 # analyze with ROS1 builtin rules
-chel analyze --platform ros1 /path/to/ros/workspace
+kelo analyze --platform ros1 /path/to/ros/workspace
 
 # analyze with ROS2 builtin rules
-chel analyze --platform ros2 /path/to/ros/workspace
+kelo analyze --platform ros2 /path/to/ros/workspace
 ```
 
 JSON output:
 
 ```bash
-chel analyze -f json /path/to/ros/workspace
+kelo analyze -f json /path/to/ros/workspace
 ```
 
 Custom rules:
 
 ```bash
 # add custom rules on top of builtin rules
-chel analyze --platform ros1 --rules /path/to/custom/rules /path/to/ros/workspace
+kelo analyze --platform ros1 --rules /path/to/custom/rules /path/to/ros/workspace
 
 # load only custom rules (disable builtin)
-chel analyze --rules /path/to/custom/rules --no-builtin /path/to/ros/workspace
+kelo analyze --rules /path/to/custom/rules --no-builtin /path/to/ros/workspace
 ```
 
 List available rules:
 
 ```bash
-chel analyze --list-rules
+kelo analyze --list-rules
 
 # include builtin rules for a specific platform
-chel analyze -p ros1 --list-rules
-chel analyze -p ros2 --list-rules
+kelo analyze -p ros1 --list-rules
+kelo analyze -p ros2 --list-rules
 ```
 
 Generate a static HTML report from JSON:
 
 ```bash
 # 1) analyze and write JSON to a file
-chel analyze -p ros1 -f json -o report.json /path/to/ros/workspace
+kelo analyze -p ros1 -f json -o report.json /path/to/ros/workspace
 
 # 2) convert JSON to a standalone HTML file
-chel report report.json -o report.html
+kelo report report.json -o report.html
 
 # or: write a directory bundle (index.html + assets/) for richer UI
-chel report report.json -o results/
+kelo report report.json -o results/
 ```
 
 Customize report sections (optional)
@@ -82,7 +82,7 @@ Customize report sections (optional)
 When writing a directory bundle (e.g. `-o results/`), you can customize the sidebar section ordering and visibility via a TOML config:
 
 ```bash
-chel report report.json -o results/ --config report.toml
+kelo report report.json -o results/ --config report.toml
 ```
 
 Example `report.toml`:

RULES.md

@@ -6,7 +6,7 @@ This document describes the TOML rule format used by Chelonian and the meaning o
 
 Rules are declared in TOML files. Each file may contain multiple `[[rules]]` entries. The loader reads rules from:
 
-- The path provided with `chel analyze --rules` (file or directory),
+- The path provided with `kelo analyze --rules` (file or directory),
 - `~/.config/chelonian/rules/*.toml`,
 - Bundled built-in rules.
 

src/commands/report.rs

@@ -12,7 +12,7 @@ use crate::models::AnalysisReport;
 
 #[derive(Args, Debug, Clone)]
 pub struct ReportArgs {
-    /// Input analysis JSON file (produced by `chel analyze --format json`)
+    /// Input analysis JSON file (produced by `kelo analyze --format json`)
     pub input: PathBuf,
 
     /// Output path.