npm - sfdx-hardis - Versions diffs - 6.1.5-beta202508282306.0 → 6.2.1 - Mend

sfdx-hardis 6.1.5-beta202508282306.0 → 6.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (14) hide show

package/CHANGELOG.md +8 -0
package/lib/commands/hardis/org/select.js +53 -6
package/lib/commands/hardis/org/select.js.map +1 -1
package/lib/commands/hardis/work/save.js +7 -8
package/lib/commands/hardis/work/save.js.map +1 -1
package/lib/common/gitProvider/index.js +1 -1
package/lib/common/gitProvider/index.js.map +1 -1
package/lib/common/metadata-utils/index.js +2 -2
package/lib/common/metadata-utils/index.js.map +1 -1
package/lib/common/utils/orgUtils.js +3 -3
package/lib/common/utils/orgUtils.js.map +1 -1
package/oclif.lock +18 -18
package/oclif.manifest.json +676 -661
package/package.json +5 -5

package/oclif.manifest.json CHANGED Viewed

@@ -57,12 +57,13 @@
         "world:hello"
       ]
     },
-    "hardis:cache:clear": {
+    "hardis:auth:login": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Clears the local cache generated by the sfdx-hardis plugin.**\n\nThis command is designed to remove temporary files, stored configurations, and other cached data that sfdx-hardis uses to optimize its operations. Clearing the cache can be beneficial for:\n\n- **Troubleshooting:** Resolving unexpected behavior or inconsistencies.\n- **Disk Space Management:** Freeing up storage on your local machine.\n- **Ensuring Fresh Data:** Guaranteeing that the plugin operates with the most current data and configurations.\n\n## Technical explanations\n\nThe command's technical implementation is straightforward:\n\n- **Direct Function Call:** It directly invokes the `clearCache()` function, which is imported from \buri../../../common/cache/index.js\buri.\n- **Cache Management Logic:** The \buriclearCache()` function encapsulates the logic for identifying and removing the specific files and directories that constitute the sfdx-hardis cache.\n",
+      "description": "\n## Command Behavior\n\n**Authenticates to a Salesforce org, primarily designed for CI/CD workflows.**\n\nThis command facilitates secure and automated logins to Salesforce organizations within continuous integration and continuous delivery pipelines. It leverages pre-configured authentication details, ensuring that CI/CD processes can interact with Salesforce without manual intervention.\n\nKey aspects:\n\n- **Configuration-Driven:** It relies on authentication variables and files set up by dedicated configuration commands:\n  - For CI/CD repositories: [Configure Org CI Authentication](https://sfdx-hardis.cloudity.com/hardis/project/configure/auth/)\n  - For Monitoring repositories: [Configure Org Monitoring](https://sfdx-hardis.cloudity.com/hardis/org/configure/monitoring/)\n- **Technical Org Support:** Supports authentication to a 'technical org' (e.g., for calling Agentforce from another org) by utilizing the `SFDX_AUTH_URL_TECHNICAL_ORG` environment variable. If this variable is set, the command authenticates to this org with the alias `TECHNICAL_ORG`.\n\nTo obtain the `SFDX_AUTH_URL_TECHNICAL_ORG` value, you can run `sf org display --verbose --json` and copy the `sfdxAuthUrl` field from the output.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical flow involves:\n\n- **Flag Parsing:** It parses command-line flags such as `instanceurl`, `devhub`, `scratchorg`, and `debug` to determine the authentication context.\n- **Authentication Hook:** It triggers an internal authentication hook (`this.config.runHook('auth', ...`)) which is responsible for executing the actual authentication logic based on the provided flags (e.g., whether it's a Dev Hub or a scratch org).\n- **Environment Variable Check:** It checks for the presence of `SFDX_AUTH_URL_TECHNICAL_ORG` or `TECHNICAL_ORG_ALIAS` environment variables.\n- **`authOrg` Utility:** If a technical org is configured, it calls the `authOrg` utility function to perform the authentication for that specific org, ensuring it's connected and available for subsequent operations.\n- **Salesforce CLI Integration:** It integrates with the Salesforce CLI's authentication mechanisms to establish and manage org connections.\n</details>\n",
       "examples": [
-        "$ sf hardis:cache:clear"
+        "$ sf hardis:auth:login",
+        "CI=true sf hardis:auth:login"
       ],
       "flags": {
         "json": {
@@ -80,6 +81,28 @@
           "multiple": false,
           "type": "option"
         },
+        "instanceurl": {
+          "char": "r",
+          "description": "URL of org instance",
+          "name": "instanceurl",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "devhub": {
+          "char": "h",
+          "description": "Also connect associated DevHub",
+          "name": "devhub",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "scratchorg": {
+          "char": "s",
+          "description": "Scratch org",
+          "name": "scratchorg",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "debug": {
           "char": "d",
           "description": "Activate debug mode (more logs)",
@@ -103,41 +126,38 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "hardis:cache:clear",
+      "id": "hardis:auth:login",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Clear sfdx-hardis cache",
-      "uiConfig": {
-        "hide": true
-      },
+      "title": "Login",
       "requiresProject": false,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
-        "cache",
-        "clear.js"
+        "auth",
+        "login.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:cache:clear",
-        "cache:hardis:clear",
-        "cache:clear:hardis",
-        "hardis:clear:cache",
-        "clear:hardis:cache",
-        "clear:cache:hardis"
+        "hardis:auth:login",
+        "auth:hardis:login",
+        "auth:login:hardis",
+        "hardis:login:auth",
+        "login:hardis:auth",
+        "login:auth:hardis"
       ]
     },
-    "hardis:config:get": {
+    "hardis:cache:clear": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Retrieves and displays the sfdx-hardis configuration for a specified level.**\n\nThis command allows you to inspect the configuration that is currently in effect for your project, which is useful for debugging and understanding how sfdx-hardis will behave.\n\n- **Configuration levels:** It can retrieve configuration from three different levels:\n  - **Project:** The configuration defined in the project's `.sfdx-hardis.yml` file.\n  - **Branch:** The configuration defined in a branch-specific configuration file (e.g., `.sfdx-hardis.production.yml`).\n  - **User:** The global user-level configuration.\n\n## Technical explanations\n\nThe command's logic is straightforward:\n\n- **`getConfig` function:** It calls the `getConfig` utility function, passing the desired configuration level as an argument.\n- **Configuration loading:** The `getConfig` function is responsible for finding the appropriate configuration file, reading its contents, and parsing it as YAML or JSON.\n- **Output:** The retrieved configuration is then displayed to the user as a JSON string.\n",
+      "description": "\n## Command Behavior\n\n**Clears the local cache generated by the sfdx-hardis plugin.**\n\nThis command is designed to remove temporary files, stored configurations, and other cached data that sfdx-hardis uses to optimize its operations. Clearing the cache can be beneficial for:\n\n- **Troubleshooting:** Resolving unexpected behavior or inconsistencies.\n- **Disk Space Management:** Freeing up storage on your local machine.\n- **Ensuring Fresh Data:** Guaranteeing that the plugin operates with the most current data and configurations.\n\n## Technical explanations\n\nThe command's technical implementation is straightforward:\n\n- **Direct Function Call:** It directly invokes the `clearCache()` function, which is imported from \buri../../../common/cache/index.js\buri.\n- **Cache Management Logic:** The \buriclearCache()` function encapsulates the logic for identifying and removing the specific files and directories that constitute the sfdx-hardis cache.\n",
       "examples": [
-        "$ sf hardis:project:deploy:sources:metadata"
+        "$ sf hardis:cache:clear"
       ],
       "flags": {
         "json": {
@@ -155,20 +175,6 @@
           "multiple": false,
           "type": "option"
         },
-        "level": {
-          "char": "l",
-          "description": "project,branch or user",
-          "name": "level",
-          "default": "project",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "project",
-            "branch",
-            "user"
-          ],
-          "type": "option"
-        },
         "debug": {
           "char": "d",
           "description": "Activate debug mode (more logs)",
@@ -192,39 +198,41 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "hardis:config:get",
+      "id": "hardis:cache:clear",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Deploy metadata sources to org",
+      "title": "Clear sfdx-hardis cache",
+      "uiConfig": {
+        "hide": true
+      },
       "requiresProject": false,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
-        "config",
-        "get.js"
+        "cache",
+        "clear.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:config:get",
-        "config:hardis:get",
-        "config:get:hardis",
-        "hardis:get:config",
-        "get:hardis:config",
-        "get:config:hardis"
+        "hardis:cache:clear",
+        "cache:hardis:clear",
+        "cache:clear:hardis",
+        "hardis:clear:cache",
+        "clear:hardis:cache",
+        "clear:cache:hardis"
       ]
     },
-    "hardis:auth:login": {
+    "hardis:config:get": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Authenticates to a Salesforce org, primarily designed for CI/CD workflows.**\n\nThis command facilitates secure and automated logins to Salesforce organizations within continuous integration and continuous delivery pipelines. It leverages pre-configured authentication details, ensuring that CI/CD processes can interact with Salesforce without manual intervention.\n\nKey aspects:\n\n- **Configuration-Driven:** It relies on authentication variables and files set up by dedicated configuration commands:\n  - For CI/CD repositories: [Configure Org CI Authentication](https://sfdx-hardis.cloudity.com/hardis/project/configure/auth/)\n  - For Monitoring repositories: [Configure Org Monitoring](https://sfdx-hardis.cloudity.com/hardis/org/configure/monitoring/)\n- **Technical Org Support:** Supports authentication to a 'technical org' (e.g., for calling Agentforce from another org) by utilizing the `SFDX_AUTH_URL_TECHNICAL_ORG` environment variable. If this variable is set, the command authenticates to this org with the alias `TECHNICAL_ORG`.\n\nTo obtain the `SFDX_AUTH_URL_TECHNICAL_ORG` value, you can run `sf org display --verbose --json` and copy the `sfdxAuthUrl` field from the output.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical flow involves:\n\n- **Flag Parsing:** It parses command-line flags such as `instanceurl`, `devhub`, `scratchorg`, and `debug` to determine the authentication context.\n- **Authentication Hook:** It triggers an internal authentication hook (`this.config.runHook('auth', ...`)) which is responsible for executing the actual authentication logic based on the provided flags (e.g., whether it's a Dev Hub or a scratch org).\n- **Environment Variable Check:** It checks for the presence of `SFDX_AUTH_URL_TECHNICAL_ORG` or `TECHNICAL_ORG_ALIAS` environment variables.\n- **`authOrg` Utility:** If a technical org is configured, it calls the `authOrg` utility function to perform the authentication for that specific org, ensuring it's connected and available for subsequent operations.\n- **Salesforce CLI Integration:** It integrates with the Salesforce CLI's authentication mechanisms to establish and manage org connections.\n</details>\n",
+      "description": "\n## Command Behavior\n\n**Retrieves and displays the sfdx-hardis configuration for a specified level.**\n\nThis command allows you to inspect the configuration that is currently in effect for your project, which is useful for debugging and understanding how sfdx-hardis will behave.\n\n- **Configuration levels:** It can retrieve configuration from three different levels:\n  - **Project:** The configuration defined in the project's `.sfdx-hardis.yml` file.\n  - **Branch:** The configuration defined in a branch-specific configuration file (e.g., `.sfdx-hardis.production.yml`).\n  - **User:** The global user-level configuration.\n\n## Technical explanations\n\nThe command's logic is straightforward:\n\n- **`getConfig` function:** It calls the `getConfig` utility function, passing the desired configuration level as an argument.\n- **Configuration loading:** The `getConfig` function is responsible for finding the appropriate configuration file, reading its contents, and parsing it as YAML or JSON.\n- **Output:** The retrieved configuration is then displayed to the user as a JSON string.\n",
       "examples": [
-        "$ sf hardis:auth:login",
-        "CI=true sf hardis:auth:login"
+        "$ sf hardis:project:deploy:sources:metadata"
       ],
       "flags": {
         "json": {
@@ -242,28 +250,20 @@
           "multiple": false,
           "type": "option"
         },
-        "instanceurl": {
-          "char": "r",
-          "description": "URL of org instance",
-          "name": "instanceurl",
+        "level": {
+          "char": "l",
+          "description": "project,branch or user",
+          "name": "level",
+          "default": "project",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "project",
+            "branch",
+            "user"
+          ],
           "type": "option"
         },
-        "devhub": {
-          "char": "h",
-          "description": "Also connect associated DevHub",
-          "name": "devhub",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "scratchorg": {
-          "char": "s",
-          "description": "Scratch org",
-          "name": "scratchorg",
-          "allowNo": false,
-          "type": "boolean"
-        },
         "debug": {
           "char": "d",
           "description": "Activate debug mode (more logs)",
@@ -287,30 +287,30 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "hardis:auth:login",
+      "id": "hardis:config:get",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Login",
+      "title": "Deploy metadata sources to org",
       "requiresProject": false,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
-        "auth",
-        "login.js"
+        "config",
+        "get.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:auth:login",
-        "auth:hardis:login",
-        "auth:login:hardis",
-        "hardis:login:auth",
-        "login:hardis:auth",
-        "login:auth:hardis"
+        "hardis:config:get",
+        "config:hardis:get",
+        "config:get:hardis",
+        "hardis:get:config",
+        "get:hardis:config",
+        "get:config:hardis"
       ]
     },
     "hardis:doc:fieldusage": {
@@ -2331,6 +2331,21 @@
           "allowNo": false,
           "type": "boolean"
         },
+        "username": {
+          "char": "t",
+          "description": "Username of the org you want to authenticate (overrides the interactive prompt)",
+          "name": "username",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "prompt-default": {
+          "char": "e",
+          "description": "Prompt to set the selected org as default",
+          "name": "prompt-default",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "debug": {
           "char": "d",
           "description": "Activate debug mode (more logs)",
@@ -4406,13 +4421,12 @@
         "ws:work:hardis"
       ]
     },
-    "hardis:git:pull-requests:extract": {
+    "hardis:doc:extract:permsetgroups": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Extracts pull request information from your Git server based on specified filtering criteria.**\n\nThis command provides a powerful way to query and retrieve details about pull requests (or merge requests, depending on your Git provider) in your repository. It's highly useful for reporting, auditing, and analyzing development workflows.\n\nKey functionalities include:\n\n- **Target Branch Filtering:** You can filter pull requests by their target branch using the `--target-branch` flag. If not specified, the command will prompt you to select one.\n- **Status Filtering:** Filter pull requests by their status: `open`, `merged`, or `abandoned` using the `--status` flag. An interactive prompt is provided if no status is specified.\n- **Minimum Date Filtering:** Use the `--min-date` flag to retrieve pull requests created or updated after a specific date.\n- **CSV Output:** The extracted pull request data is generated into a CSV file, which can be used for further analysis in spreadsheet software.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves interacting with a Git provider's API:\n\n- **Git Provider Abstraction:** It uses the `GitProvider.getInstance(true)` to abstract away the specifics of different Git platforms (e.g., GitHub, GitLab, Azure DevOps). This ensures the command can work across various environments.\n- **API Calls:** The `gitProvider.listPullRequests()` method is called with a `prConstraint` object that encapsulates the filtering criteria (target branch, minimum date, status).\n- **Interactive Prompts:** The `prompts` library is used to interactively gather input from the user for the target branch and pull request status if they are not provided as command-line flags.\n- **Date Handling:** The `moment` library is used to parse and handle date inputs for the `--min-date` flag.\n- **CSV Generation:** The `generateCsvFile` utility is responsible for converting the retrieved pull request data into a CSV format, and `generateReportPath` determines the output file location.\n- **Error Handling:** It includes error handling for cases where a Git provider cannot be identified.\n</details>\n",
+      "description": "\n## Command Behavior\n\n**Extracts and documents Salesforce Permission Set Groups and their assigned Permission Sets.**\n\nThis command generates two types of output: a CSV file and a Markdown file, providing a clear overview of how Permission Set Groups are structured and what Permission Sets they contain within your Salesforce project. This is particularly useful for:\n\n- **Documentation:** Creating human-readable documentation of your permission architecture.\n- **Auditing:** Understanding the composition of permission sets for security and compliance checks.\n- **Analysis:** Gaining insights into how permissions are bundled and assigned in your Salesforce environment.\n\nThe generated CSV file provides a structured, machine-readable format, while the Markdown file offers a more descriptive, human-friendly view, including the group's name, label, description, and a list of its constituent permission sets.\n\n## Technical explanations\n\nThe command performs the following technical steps:\n\n- **File Discovery:** It uses `glob` to find all `.permissionsetgroup-meta.xml` files within the current working directory, respecting `.gitignore` patterns.\n- **XML Parsing:** For each discovered Permission Set Group XML file, it parses the XML content using `parseXmlFile` to extract relevant information such as the group's name, label, description, and the names of the Permission Sets it contains.\n- **Data Structuring:** The extracted data is then structured into a list of objects, making it easy to process.\n- **CSV Generation:** It constructs a CSV file with two columns: 'Permission set group' and 'Permission sets'. The 'Permission sets' column lists all assigned permission sets for each group, enclosed in quotes and separated by commas. The CSV file is saved to a temporary directory or a user-specified path.\n- **Markdown Generation:** It generates a Markdown file (`docs/permission-set-groups.md`) that includes a title, a table of contents, and detailed sections for each Permission Set Group. Each section lists the group's name, label, description, and a bulleted list of its assigned Permission Sets.\n- **File System Operations:** It uses `fs-extra` to ensure output directories exist and to write the generated CSV and Markdown files.\n- **VS Code Integration:** It uses `WebSocketClient.requestOpenFile` to automatically open the generated CSV and Markdown files in VS Code, enhancing the user experience.\n",
       "examples": [
-        "$ sf hardis:git:pull-requests:extract",
-        "$ sf hardis:git:pull-requests:extract --target-branch main --status merged"
+        "$ sf hardis:doc:extract:permsetgroups"
       ],
       "flags": {
         "json": {
@@ -4430,35 +4444,6 @@
           "multiple": false,
           "type": "option"
         },
-        "target-branch": {
-          "char": "t",
-          "description": "Target branch of PRs",
-          "name": "target-branch",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "status": {
-          "char": "x",
-          "description": "Status of the PR",
-          "name": "status",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "open",
-            "merged",
-            "abandoned"
-          ],
-          "type": "option"
-        },
-        "min-date": {
-          "char": "m",
-          "description": "Minimum date for PR",
-          "name": "min-date",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "outputfile": {
           "char": "f",
           "description": "Force the path and name of output report file. Must end with .csv",
@@ -4490,57 +4475,57 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "hardis:git:pull-requests:extract",
+      "id": "hardis:doc:extract:permsetgroups",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Extract pull requests",
+      "title": "Generate project documentation",
       "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
-        "git",
-        "pull-requests",
-        "extract.js"
+        "doc",
+        "extract",
+        "permsetgroups.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:git:pull-requests:extract",
-        "git:hardis:pull-requests:extract",
-        "git:pull-requests:hardis:extract",
-        "git:pull-requests:extract:hardis",
-        "hardis:pull-requests:git:extract",
-        "pull-requests:hardis:git:extract",
-        "pull-requests:git:hardis:extract",
-        "pull-requests:git:extract:hardis",
-        "hardis:pull-requests:extract:git",
-        "pull-requests:hardis:extract:git",
-        "pull-requests:extract:hardis:git",
-        "pull-requests:extract:git:hardis",
-        "hardis:git:extract:pull-requests",
-        "git:hardis:extract:pull-requests",
-        "git:extract:hardis:pull-requests",
-        "git:extract:pull-requests:hardis",
-        "hardis:extract:git:pull-requests",
-        "extract:hardis:git:pull-requests",
-        "extract:git:hardis:pull-requests",
-        "extract:git:pull-requests:hardis",
-        "hardis:extract:pull-requests:git",
-        "extract:hardis:pull-requests:git",
-        "extract:pull-requests:hardis:git",
-        "extract:pull-requests:git:hardis"
+        "hardis:doc:extract:permsetgroups",
+        "doc:hardis:extract:permsetgroups",
+        "doc:extract:hardis:permsetgroups",
+        "doc:extract:permsetgroups:hardis",
+        "hardis:extract:doc:permsetgroups",
+        "extract:hardis:doc:permsetgroups",
+        "extract:doc:hardis:permsetgroups",
+        "extract:doc:permsetgroups:hardis",
+        "hardis:extract:permsetgroups:doc",
+        "extract:hardis:permsetgroups:doc",
+        "extract:permsetgroups:hardis:doc",
+        "extract:permsetgroups:doc:hardis",
+        "hardis:doc:permsetgroups:extract",
+        "doc:hardis:permsetgroups:extract",
+        "doc:permsetgroups:hardis:extract",
+        "doc:permsetgroups:extract:hardis",
+        "hardis:permsetgroups:doc:extract",
+        "permsetgroups:hardis:doc:extract",
+        "permsetgroups:doc:hardis:extract",
+        "permsetgroups:doc:extract:hardis",
+        "hardis:permsetgroups:extract:doc",
+        "permsetgroups:hardis:extract:doc",
+        "permsetgroups:extract:hardis:doc",
+        "permsetgroups:extract:doc:hardis"
       ]
     },
-    "hardis:doc:extract:permsetgroups": {
+    "hardis:doc:plugin:generate": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Extracts and documents Salesforce Permission Set Groups and their assigned Permission Sets.**\n\nThis command generates two types of output: a CSV file and a Markdown file, providing a clear overview of how Permission Set Groups are structured and what Permission Sets they contain within your Salesforce project. This is particularly useful for:\n\n- **Documentation:** Creating human-readable documentation of your permission architecture.\n- **Auditing:** Understanding the composition of permission sets for security and compliance checks.\n- **Analysis:** Gaining insights into how permissions are bundled and assigned in your Salesforce environment.\n\nThe generated CSV file provides a structured, machine-readable format, while the Markdown file offers a more descriptive, human-friendly view, including the group's name, label, description, and a list of its constituent permission sets.\n\n## Technical explanations\n\nThe command performs the following technical steps:\n\n- **File Discovery:** It uses `glob` to find all `.permissionsetgroup-meta.xml` files within the current working directory, respecting `.gitignore` patterns.\n- **XML Parsing:** For each discovered Permission Set Group XML file, it parses the XML content using `parseXmlFile` to extract relevant information such as the group's name, label, description, and the names of the Permission Sets it contains.\n- **Data Structuring:** The extracted data is then structured into a list of objects, making it easy to process.\n- **CSV Generation:** It constructs a CSV file with two columns: 'Permission set group' and 'Permission sets'. The 'Permission sets' column lists all assigned permission sets for each group, enclosed in quotes and separated by commas. The CSV file is saved to a temporary directory or a user-specified path.\n- **Markdown Generation:** It generates a Markdown file (`docs/permission-set-groups.md`) that includes a title, a table of contents, and detailed sections for each Permission Set Group. Each section lists the group's name, label, description, and a bulleted list of its assigned Permission Sets.\n- **File System Operations:** It uses `fs-extra` to ensure output directories exist and to write the generated CSV and Markdown files.\n- **VS Code Integration:** It uses `WebSocketClient.requestOpenFile` to automatically open the generated CSV and Markdown files in VS Code, enhancing the user experience.\n",
+      "description": "\n## Command Behavior\n\n**Generates Markdown documentation for an SF CLI plugin, ready for conversion into HTML with MkDocs.**\n\nThis command automates the creation of comprehensive documentation for your Salesforce CLI plugin. It processes your plugin's commands and their flags to generate structured Markdown files, which can then be used with MkDocs to produce a professional-looking website.\n\nKey functionalities:\n\n- **Command Documentation:** Generates a dedicated Markdown file for each command, including its description, parameters (flags), and examples.\n- **Index and Commands Pages:** Creates an `index.md` and `commands.md` file that list all available commands, providing an overview and easy navigation.\n- **MkDocs Integration:** Sets up the basic MkDocs project structure and updates the `mkdocs.yml` navigation to include the generated command documentation.\n- **Default File Copying:** Copies essential MkDocs configuration files and GitHub Actions workflows to your project, streamlining the setup for continuous documentation deployment.\n\n**Post-Generation Steps:**\n\nAfter the initial run, you will need to manually update:\n\n- `mkdocs.yml`: Customize the project title, theme, and other MkDocs settings.\n- `.github/workflows/build-deploy-docs.yml`: Configure the GitHub Actions workflow for automatic documentation deployment.\n- `docs/javascripts/gtag.js`: If desired, set up Google Analytics tracking.\n\nFinally, activate GitHub Pages with `gh_pages` as the target branch. This will enable automatic documentation rebuilding and publishing to GitHub Pages upon each merge into your `master`/`main` branch.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **Plugin Configuration Loading:** It loads the SF CLI plugin's configuration using `@oclif/core`'s `Config.load()`, which provides access to all registered commands and their metadata.\n- **Command Iteration:** It iterates through each command defined in the plugin's configuration.\n- **Markdown File Generation:** For each command, it constructs a Markdown file (`.md`) containing:\n  - The command ID as the main heading.\n  - The command's `description` property.\n  - A table of parameters (flags), including their name, type, description, default value, required status, and available options. It dynamically extracts this information from the command's `flags` property.\n  - Code blocks for each example provided in the command's `examples` property.\n- **Navigation Structure:** It builds a nested JavaScript object (`commandsNav`) that mirrors the command hierarchy, which is then converted to YAML and inserted into `mkdocs.yml` to create the navigation menu.\n- **Index and Commands Page Generation:** It reads the project's `README.md` and extracts relevant sections to create the `index.md` file. It also generates a separate `commands.md` file listing all commands.\n- **File System Operations:** It uses `fs-extra` to create directories, copy default MkDocs files (`defaults/mkdocs`), and write the generated Markdown and YAML files.\n- **YAML Serialization:** It uses `js-yaml` to serialize the navigation object into YAML format for `mkdocs.yml`.\n</details>\n",
       "examples": [
-        "$ sf hardis:doc:extract:permsetgroups"
+        "$ sf hardis:doc:plugin:generate"
       ],
       "flags": {
         "json": {
@@ -4558,14 +4543,6 @@
           "multiple": false,
           "type": "option"
         },
-        "outputfile": {
-          "char": "f",
-          "description": "Force the path and name of output report file. Must end with .csv",
-          "name": "outputfile",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "debug": {
           "char": "d",
           "description": "Activate debug mode (more logs)",
@@ -4589,57 +4566,58 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "hardis:doc:extract:permsetgroups",
+      "id": "hardis:doc:plugin:generate",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Generate project documentation",
-      "requiresProject": true,
+      "title": "Generate SF Cli Plugin Documentation",
+      "requiresProject": false,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
         "doc",
-        "extract",
-        "permsetgroups.js"
+        "plugin",
+        "generate.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:doc:extract:permsetgroups",
-        "doc:hardis:extract:permsetgroups",
-        "doc:extract:hardis:permsetgroups",
-        "doc:extract:permsetgroups:hardis",
-        "hardis:extract:doc:permsetgroups",
-        "extract:hardis:doc:permsetgroups",
-        "extract:doc:hardis:permsetgroups",
-        "extract:doc:permsetgroups:hardis",
-        "hardis:extract:permsetgroups:doc",
-        "extract:hardis:permsetgroups:doc",
-        "extract:permsetgroups:hardis:doc",
-        "extract:permsetgroups:doc:hardis",
-        "hardis:doc:permsetgroups:extract",
-        "doc:hardis:permsetgroups:extract",
-        "doc:permsetgroups:hardis:extract",
-        "doc:permsetgroups:extract:hardis",
-        "hardis:permsetgroups:doc:extract",
-        "permsetgroups:hardis:doc:extract",
-        "permsetgroups:doc:hardis:extract",
-        "permsetgroups:doc:extract:hardis",
-        "hardis:permsetgroups:extract:doc",
-        "permsetgroups:hardis:extract:doc",
-        "permsetgroups:extract:hardis:doc",
-        "permsetgroups:extract:doc:hardis"
+        "hardis:doc:plugin:generate",
+        "doc:hardis:plugin:generate",
+        "doc:plugin:hardis:generate",
+        "doc:plugin:generate:hardis",
+        "hardis:plugin:doc:generate",
+        "plugin:hardis:doc:generate",
+        "plugin:doc:hardis:generate",
+        "plugin:doc:generate:hardis",
+        "hardis:plugin:generate:doc",
+        "plugin:hardis:generate:doc",
+        "plugin:generate:hardis:doc",
+        "plugin:generate:doc:hardis",
+        "hardis:doc:generate:plugin",
+        "doc:hardis:generate:plugin",
+        "doc:generate:hardis:plugin",
+        "doc:generate:plugin:hardis",
+        "hardis:generate:doc:plugin",
+        "generate:hardis:doc:plugin",
+        "generate:doc:hardis:plugin",
+        "generate:doc:plugin:hardis",
+        "hardis:generate:plugin:doc",
+        "generate:hardis:plugin:doc",
+        "generate:plugin:hardis:doc",
+        "generate:plugin:doc:hardis"
       ]
     },
-    "hardis:doc:plugin:generate": {
+    "hardis:git:pull-requests:extract": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Generates Markdown documentation for an SF CLI plugin, ready for conversion into HTML with MkDocs.**\n\nThis command automates the creation of comprehensive documentation for your Salesforce CLI plugin. It processes your plugin's commands and their flags to generate structured Markdown files, which can then be used with MkDocs to produce a professional-looking website.\n\nKey functionalities:\n\n- **Command Documentation:** Generates a dedicated Markdown file for each command, including its description, parameters (flags), and examples.\n- **Index and Commands Pages:** Creates an `index.md` and `commands.md` file that list all available commands, providing an overview and easy navigation.\n- **MkDocs Integration:** Sets up the basic MkDocs project structure and updates the `mkdocs.yml` navigation to include the generated command documentation.\n- **Default File Copying:** Copies essential MkDocs configuration files and GitHub Actions workflows to your project, streamlining the setup for continuous documentation deployment.\n\n**Post-Generation Steps:**\n\nAfter the initial run, you will need to manually update:\n\n- `mkdocs.yml`: Customize the project title, theme, and other MkDocs settings.\n- `.github/workflows/build-deploy-docs.yml`: Configure the GitHub Actions workflow for automatic documentation deployment.\n- `docs/javascripts/gtag.js`: If desired, set up Google Analytics tracking.\n\nFinally, activate GitHub Pages with `gh_pages` as the target branch. This will enable automatic documentation rebuilding and publishing to GitHub Pages upon each merge into your `master`/`main` branch.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **Plugin Configuration Loading:** It loads the SF CLI plugin's configuration using `@oclif/core`'s `Config.load()`, which provides access to all registered commands and their metadata.\n- **Command Iteration:** It iterates through each command defined in the plugin's configuration.\n- **Markdown File Generation:** For each command, it constructs a Markdown file (`.md`) containing:\n  - The command ID as the main heading.\n  - The command's `description` property.\n  - A table of parameters (flags), including their name, type, description, default value, required status, and available options. It dynamically extracts this information from the command's `flags` property.\n  - Code blocks for each example provided in the command's `examples` property.\n- **Navigation Structure:** It builds a nested JavaScript object (`commandsNav`) that mirrors the command hierarchy, which is then converted to YAML and inserted into `mkdocs.yml` to create the navigation menu.\n- **Index and Commands Page Generation:** It reads the project's `README.md` and extracts relevant sections to create the `index.md` file. It also generates a separate `commands.md` file listing all commands.\n- **File System Operations:** It uses `fs-extra` to create directories, copy default MkDocs files (`defaults/mkdocs`), and write the generated Markdown and YAML files.\n- **YAML Serialization:** It uses `js-yaml` to serialize the navigation object into YAML format for `mkdocs.yml`.\n</details>\n",
+      "description": "\n## Command Behavior\n\n**Extracts pull request information from your Git server based on specified filtering criteria.**\n\nThis command provides a powerful way to query and retrieve details about pull requests (or merge requests, depending on your Git provider) in your repository. It's highly useful for reporting, auditing, and analyzing development workflows.\n\nKey functionalities include:\n\n- **Target Branch Filtering:** You can filter pull requests by their target branch using the `--target-branch` flag. If not specified, the command will prompt you to select one.\n- **Status Filtering:** Filter pull requests by their status: `open`, `merged`, or `abandoned` using the `--status` flag. An interactive prompt is provided if no status is specified.\n- **Minimum Date Filtering:** Use the `--min-date` flag to retrieve pull requests created or updated after a specific date.\n- **CSV Output:** The extracted pull request data is generated into a CSV file, which can be used for further analysis in spreadsheet software.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves interacting with a Git provider's API:\n\n- **Git Provider Abstraction:** It uses the `GitProvider.getInstance(true)` to abstract away the specifics of different Git platforms (e.g., GitHub, GitLab, Azure DevOps). This ensures the command can work across various environments.\n- **API Calls:** The `gitProvider.listPullRequests()` method is called with a `prConstraint` object that encapsulates the filtering criteria (target branch, minimum date, status).\n- **Interactive Prompts:** The `prompts` library is used to interactively gather input from the user for the target branch and pull request status if they are not provided as command-line flags.\n- **Date Handling:** The `moment` library is used to parse and handle date inputs for the `--min-date` flag.\n- **CSV Generation:** The `generateCsvFile` utility is responsible for converting the retrieved pull request data into a CSV format, and `generateReportPath` determines the output file location.\n- **Error Handling:** It includes error handling for cases where a Git provider cannot be identified.\n</details>\n",
       "examples": [
-        "$ sf hardis:doc:plugin:generate"
+        "$ sf hardis:git:pull-requests:extract",
+        "$ sf hardis:git:pull-requests:extract --target-branch main --status merged"
       ],
       "flags": {
         "json": {
@@ -4657,6 +4635,43 @@
           "multiple": false,
           "type": "option"
         },
+        "target-branch": {
+          "char": "t",
+          "description": "Target branch of PRs",
+          "name": "target-branch",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "status": {
+          "char": "x",
+          "description": "Status of the PR",
+          "name": "status",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "open",
+            "merged",
+            "abandoned"
+          ],
+          "type": "option"
+        },
+        "min-date": {
+          "char": "m",
+          "description": "Minimum date for PR",
+          "name": "min-date",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "outputfile": {
+          "char": "f",
+          "description": "Force the path and name of output report file. Must end with .csv",
+          "name": "outputfile",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "debug": {
           "char": "d",
           "description": "Activate debug mode (more logs)",
@@ -4680,49 +4695,49 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "hardis:doc:plugin:generate",
+      "id": "hardis:git:pull-requests:extract",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Generate SF Cli Plugin Documentation",
-      "requiresProject": false,
+      "title": "Extract pull requests",
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
-        "doc",
-        "plugin",
-        "generate.js"
+        "git",
+        "pull-requests",
+        "extract.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:doc:plugin:generate",
-        "doc:hardis:plugin:generate",
-        "doc:plugin:hardis:generate",
-        "doc:plugin:generate:hardis",
-        "hardis:plugin:doc:generate",
-        "plugin:hardis:doc:generate",
-        "plugin:doc:hardis:generate",
-        "plugin:doc:generate:hardis",
-        "hardis:plugin:generate:doc",
-        "plugin:hardis:generate:doc",
-        "plugin:generate:hardis:doc",
-        "plugin:generate:doc:hardis",
-        "hardis:doc:generate:plugin",
-        "doc:hardis:generate:plugin",
-        "doc:generate:hardis:plugin",
-        "doc:generate:plugin:hardis",
-        "hardis:generate:doc:plugin",
-        "generate:hardis:doc:plugin",
-        "generate:doc:hardis:plugin",
-        "generate:doc:plugin:hardis",
-        "hardis:generate:plugin:doc",
-        "generate:hardis:plugin:doc",
-        "generate:plugin:hardis:doc",
-        "generate:plugin:doc:hardis"
+        "hardis:git:pull-requests:extract",
+        "git:hardis:pull-requests:extract",
+        "git:pull-requests:hardis:extract",
+        "git:pull-requests:extract:hardis",
+        "hardis:pull-requests:git:extract",
+        "pull-requests:hardis:git:extract",
+        "pull-requests:git:hardis:extract",
+        "pull-requests:git:extract:hardis",
+        "hardis:pull-requests:extract:git",
+        "pull-requests:hardis:extract:git",
+        "pull-requests:extract:hardis:git",
+        "pull-requests:extract:git:hardis",
+        "hardis:git:extract:pull-requests",
+        "git:hardis:extract:pull-requests",
+        "git:extract:hardis:pull-requests",
+        "git:extract:pull-requests:hardis",
+        "hardis:extract:git:pull-requests",
+        "extract:hardis:git:pull-requests",
+        "extract:git:hardis:pull-requests",
+        "extract:git:pull-requests:hardis",
+        "hardis:extract:pull-requests:git",
+        "extract:hardis:pull-requests:git",
+        "extract:pull-requests:hardis:git",
+        "extract:pull-requests:git:hardis"
       ]
     },
     "hardis:org:community:update": {
@@ -9676,12 +9691,12 @@
         "auth:configure:project:hardis"
       ]
     },
-    "hardis:project:clean:emptyitems": {
+    "hardis:project:convert:profilestopermsets": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Removes empty or irrelevant metadata items from your Salesforce DX project sources.**\n\nThis command helps maintain a clean and efficient Salesforce codebase by deleting metadata files that are essentially empty or contain no meaningful configuration. These files can sometimes be generated during retrieval processes or remain after refactoring, contributing to unnecessary clutter in your project.\n\nKey functionalities:\n\n- **Targeted Cleaning:** Specifically targets and removes empty instances of:\n  - Global Value Set Translations (`.globalValueSetTranslation-meta.xml`)\n  - Standard Value Sets (`.standardValueSet-meta.xml`)\n  - Sharing Rules (`.sharingRules-meta.xml`)\n- **Content-Based Deletion:** It checks the XML content of these files for the presence of specific tags (e.g., `valueTranslation` for Global Value Set Translations) to determine if they are truly empty or lack relevant data.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **File Discovery:** Uses `glob` to find files matching predefined patterns for Global Value Set Translations, Standard Value Sets, and Sharing Rules within the specified root folder (defaults to `force-app`).\n- **XML Parsing:** For each matching file, it reads and parses the XML content using `parseXmlFile`.\n- **Content Validation:** It then checks the parsed XML object for the existence of specific nested properties (e.g., `xmlContent.GlobalValueSetTranslation.valueTranslation`). If these properties are missing or empty, the file is considered empty.\n- **File Deletion:** If a file is determined to be empty, it is removed from the file system using `fs.remove`.\n- **Logging:** Provides clear messages about which files are being removed and a summary of the total number of items cleaned.\n</details>\n",
+      "description": "\n## Command Behavior\n\n**Converts existing Salesforce Profiles into Permission Sets, facilitating a more granular and recommended security model.**\n\nThis command helps in migrating permissions from Profiles to Permission Sets, which is a best practice for managing user access in Salesforce. It creates a new Permission Set for each specified Profile, adopting a naming convention of `PS_PROFILENAME`.\n\nKey functionalities:\n\n- **Profile to Permission Set Conversion:** Automatically extracts permissions from a Profile and creates a corresponding Permission Set.\n- **Naming Convention:** New Permission Sets are named with a `PS_` prefix followed by the Profile name (e.g., `PS_Standard_User`).\n- **Exclusion Filter:** Allows you to exclude specific Profiles from the conversion process using the `--except` flag.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **External Plugin Integration:** It relies on the `shane-sfdx-plugins` (specifically the `sf shane:profile:convert` command) to perform the actual conversion.\n- **File System Scan:** It reads the contents of the `force-app/main/default/profiles` directory to identify all available Profile metadata files.\n- **Command Execution:** For each identified Profile (that is not excluded), it constructs and executes the `sf shane:profile:convert` command with the appropriate Profile name and desired Permission Set name.\n- **Error Handling:** Includes basic error handling for the external command execution.\n</details>\n",
       "examples": [
-        "$ sf hardis:project:clean:emptyitems"
+        "$ sf hardis:project:convert:profilestopermsets"
       ],
       "flags": {
         "json": {
@@ -9699,13 +9714,13 @@
           "multiple": false,
           "type": "option"
         },
-        "folder": {
-          "char": "f",
-          "description": "Root folder",
-          "name": "folder",
-          "default": "force-app",
+        "except": {
+          "char": "e",
+          "description": "List of filters",
+          "name": "except",
+          "default": [],
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
           "type": "option"
         },
         "debug": {
@@ -9731,58 +9746,161 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "hardis:project:clean:emptyitems",
+      "id": "hardis:project:convert:profilestopermsets",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Clean retrieved empty items in dx sources",
+      "title": "Convert Profiles into Permission Sets",
       "requiresProject": true,
+      "requiresSfdxPlugins": [
+        "shane-sfdx-plugins"
+      ],
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
         "project",
-        "clean",
-        "emptyitems.js"
+        "convert",
+        "profilestopermsets.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:project:clean:emptyitems",
-        "project:hardis:clean:emptyitems",
-        "project:clean:hardis:emptyitems",
-        "project:clean:emptyitems:hardis",
-        "hardis:clean:project:emptyitems",
-        "clean:hardis:project:emptyitems",
-        "clean:project:hardis:emptyitems",
-        "clean:project:emptyitems:hardis",
-        "hardis:clean:emptyitems:project",
-        "clean:hardis:emptyitems:project",
-        "clean:emptyitems:hardis:project",
-        "clean:emptyitems:project:hardis",
-        "hardis:project:emptyitems:clean",
-        "project:hardis:emptyitems:clean",
-        "project:emptyitems:hardis:clean",
-        "project:emptyitems:clean:hardis",
-        "hardis:emptyitems:project:clean",
-        "emptyitems:hardis:project:clean",
-        "emptyitems:project:hardis:clean",
-        "emptyitems:project:clean:hardis",
-        "hardis:emptyitems:clean:project",
-        "emptyitems:hardis:clean:project",
-        "emptyitems:clean:hardis:project",
-        "emptyitems:clean:project:hardis"
+        "hardis:project:convert:profilestopermsets",
+        "project:hardis:convert:profilestopermsets",
+        "project:convert:hardis:profilestopermsets",
+        "project:convert:profilestopermsets:hardis",
+        "hardis:convert:project:profilestopermsets",
+        "convert:hardis:project:profilestopermsets",
+        "convert:project:hardis:profilestopermsets",
+        "convert:project:profilestopermsets:hardis",
+        "hardis:convert:profilestopermsets:project",
+        "convert:hardis:profilestopermsets:project",
+        "convert:profilestopermsets:hardis:project",
+        "convert:profilestopermsets:project:hardis",
+        "hardis:project:profilestopermsets:convert",
+        "project:hardis:profilestopermsets:convert",
+        "project:profilestopermsets:hardis:convert",
+        "project:profilestopermsets:convert:hardis",
+        "hardis:profilestopermsets:project:convert",
+        "profilestopermsets:hardis:project:convert",
+        "profilestopermsets:project:hardis:convert",
+        "profilestopermsets:project:convert:hardis",
+        "hardis:profilestopermsets:convert:project",
+        "profilestopermsets:hardis:convert:project",
+        "profilestopermsets:convert:hardis:project",
+        "profilestopermsets:convert:project:hardis"
       ]
     },
-    "hardis:project:clean:filter-xml-content": {
+    "hardis:project:clean:emptyitems": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Filters the content of Salesforce metadata XML files to remove specific elements, enabling more granular deployments.**\n\nThis command addresses a common challenge in Salesforce development: deploying only a subset of metadata from an XML file when the target org might not support all elements or when certain elements are not desired. It allows you to define rules in a JSON configuration file to remove unwanted XML nodes.\n\nKey functionalities:\n\n- **Configurable Filtering:** Uses a JSON configuration file (e.g., `filter-config.json`) to define which XML elements to remove. This configuration specifies the XML tags to target and the values within those tags that should trigger removal.\n- **Targeted File Processing:** Processes XML files within a specified input folder (defaults to current directory) and writes the filtered content to an output folder.\n- **Example Use Cases:** Useful for scenarios like:\n  - Removing references to features not enabled in the target org.\n  - Stripping out specific profile permissions or field-level security settings.\n  - Cleaning up metadata that is not relevant to a particular deployment.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **Configuration Loading:** Reads the `filter-config.json` file, which contains an array of `filters`. Each filter defines a `name`, `description`, `folders` (where to apply the filter), `file_extensions`, and an `exclude_list`.\n- **File System Operations:** Copies the input folder to an output folder (if different) to avoid modifying original files directly. It then iterates through the files in the output folder that match the specified file extensions.\n- **XML Parsing and Manipulation:** For each matching XML file:\n  - It uses `xml2js.Parser` to parse the XML content into a JavaScript object.\n  - It recursively traverses the JavaScript object, applying the `filterElement` function.\n  - The `filterElement` function checks for `type_tag` and `identifier_tag` defined in the `exclude_list`. If a match is found and the value is in the `excludeDef.values`, the element is removed from the XML structure.\n  - After filtering, it uses `writeXmlFile` to write the modified JavaScript object back to the XML file.\n- **Logging:** Provides detailed logs about the filtering process, including which files are being processed and which elements are being filtered.\n- **Summary Reporting:** Tracks and reports on the files that have been updated due to filtering.\n</details>\n",
+      "description": "\n## Command Behavior\n\n**Removes empty or irrelevant metadata items from your Salesforce DX project sources.**\n\nThis command helps maintain a clean and efficient Salesforce codebase by deleting metadata files that are essentially empty or contain no meaningful configuration. These files can sometimes be generated during retrieval processes or remain after refactoring, contributing to unnecessary clutter in your project.\n\nKey functionalities:\n\n- **Targeted Cleaning:** Specifically targets and removes empty instances of:\n  - Global Value Set Translations (`.globalValueSetTranslation-meta.xml`)\n  - Standard Value Sets (`.standardValueSet-meta.xml`)\n  - Sharing Rules (`.sharingRules-meta.xml`)\n- **Content-Based Deletion:** It checks the XML content of these files for the presence of specific tags (e.g., `valueTranslation` for Global Value Set Translations) to determine if they are truly empty or lack relevant data.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **File Discovery:** Uses `glob` to find files matching predefined patterns for Global Value Set Translations, Standard Value Sets, and Sharing Rules within the specified root folder (defaults to `force-app`).\n- **XML Parsing:** For each matching file, it reads and parses the XML content using `parseXmlFile`.\n- **Content Validation:** It then checks the parsed XML object for the existence of specific nested properties (e.g., `xmlContent.GlobalValueSetTranslation.valueTranslation`). If these properties are missing or empty, the file is considered empty.\n- **File Deletion:** If a file is determined to be empty, it is removed from the file system using `fs.remove`.\n- **Logging:** Provides clear messages about which files are being removed and a summary of the total number of items cleaned.\n</details>\n",
       "examples": [
-        "sf hardis:project:clean:filter-xml-content -i \"./mdapi_output\"",
-        "sf hardis:project:clean:filter-xml-content -i \"retrieveUnpackaged\""
+        "$ sf hardis:project:clean:emptyitems"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "folder": {
+          "char": "f",
+          "description": "Root folder",
+          "name": "folder",
+          "default": "force-app",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "debug": {
+          "char": "d",
+          "description": "Activate debug mode (more logs)",
+          "name": "debug",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "websocket": {
+          "description": "Websocket host:port for VsCode SFDX Hardis UI integration",
+          "name": "websocket",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "skipauth": {
+          "description": "Skip authentication check when a default username is required",
+          "name": "skipauth",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "hardis:project:clean:emptyitems",
+      "pluginAlias": "sfdx-hardis",
+      "pluginName": "sfdx-hardis",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "title": "Clean retrieved empty items in dx sources",
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "hardis",
+        "project",
+        "clean",
+        "emptyitems.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "hardis:project:clean:emptyitems",
+        "project:hardis:clean:emptyitems",
+        "project:clean:hardis:emptyitems",
+        "project:clean:emptyitems:hardis",
+        "hardis:clean:project:emptyitems",
+        "clean:hardis:project:emptyitems",
+        "clean:project:hardis:emptyitems",
+        "clean:project:emptyitems:hardis",
+        "hardis:clean:emptyitems:project",
+        "clean:hardis:emptyitems:project",
+        "clean:emptyitems:hardis:project",
+        "clean:emptyitems:project:hardis",
+        "hardis:project:emptyitems:clean",
+        "project:hardis:emptyitems:clean",
+        "project:emptyitems:hardis:clean",
+        "project:emptyitems:clean:hardis",
+        "hardis:emptyitems:project:clean",
+        "emptyitems:hardis:project:clean",
+        "emptyitems:project:hardis:clean",
+        "emptyitems:project:clean:hardis",
+        "hardis:emptyitems:clean:project",
+        "emptyitems:hardis:clean:project",
+        "emptyitems:clean:hardis:project",
+        "emptyitems:clean:project:hardis"
+      ]
+    },
+    "hardis:project:clean:filter-xml-content": {
+      "aliases": [],
+      "args": {},
+      "description": "\n## Command Behavior\n\n**Filters the content of Salesforce metadata XML files to remove specific elements, enabling more granular deployments.**\n\nThis command addresses a common challenge in Salesforce development: deploying only a subset of metadata from an XML file when the target org might not support all elements or when certain elements are not desired. It allows you to define rules in a JSON configuration file to remove unwanted XML nodes.\n\nKey functionalities:\n\n- **Configurable Filtering:** Uses a JSON configuration file (e.g., `filter-config.json`) to define which XML elements to remove. This configuration specifies the XML tags to target and the values within those tags that should trigger removal.\n- **Targeted File Processing:** Processes XML files within a specified input folder (defaults to current directory) and writes the filtered content to an output folder.\n- **Example Use Cases:** Useful for scenarios like:\n  - Removing references to features not enabled in the target org.\n  - Stripping out specific profile permissions or field-level security settings.\n  - Cleaning up metadata that is not relevant to a particular deployment.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **Configuration Loading:** Reads the `filter-config.json` file, which contains an array of `filters`. Each filter defines a `name`, `description`, `folders` (where to apply the filter), `file_extensions`, and an `exclude_list`.\n- **File System Operations:** Copies the input folder to an output folder (if different) to avoid modifying original files directly. It then iterates through the files in the output folder that match the specified file extensions.\n- **XML Parsing and Manipulation:** For each matching XML file:\n  - It uses `xml2js.Parser` to parse the XML content into a JavaScript object.\n  - It recursively traverses the JavaScript object, applying the `filterElement` function.\n  - The `filterElement` function checks for `type_tag` and `identifier_tag` defined in the `exclude_list`. If a match is found and the value is in the `excludeDef.values`, the element is removed from the XML structure.\n  - After filtering, it uses `writeXmlFile` to write the modified JavaScript object back to the XML file.\n- **Logging:** Provides detailed logs about the filtering process, including which files are being processed and which elements are being filtered.\n- **Summary Reporting:** Tracks and reports on the files that have been updated due to filtering.\n</details>\n",
+      "examples": [
+        "sf hardis:project:clean:filter-xml-content -i \"./mdapi_output\"",
+        "sf hardis:project:clean:filter-xml-content -i \"retrieveUnpackaged\""
       ],
       "flags": {
         "json": {
@@ -11161,12 +11279,14 @@
         "xml:clean:project:hardis"
       ]
     },
-    "hardis:project:convert:profilestopermsets": {
+    "hardis:project:deploy:notify": {
       "aliases": [],
       "args": {},
-      "description": "\n## Command Behavior\n\n**Converts existing Salesforce Profiles into Permission Sets, facilitating a more granular and recommended security model.**\n\nThis command helps in migrating permissions from Profiles to Permission Sets, which is a best practice for managing user access in Salesforce. It creates a new Permission Set for each specified Profile, adopting a naming convention of `PS_PROFILENAME`.\n\nKey functionalities:\n\n- **Profile to Permission Set Conversion:** Automatically extracts permissions from a Profile and creates a corresponding Permission Set.\n- **Naming Convention:** New Permission Sets are named with a `PS_` prefix followed by the Profile name (e.g., `PS_Standard_User`).\n- **Exclusion Filter:** Allows you to exclude specific Profiles from the conversion process using the `--except` flag.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **External Plugin Integration:** It relies on the `shane-sfdx-plugins` (specifically the `sf shane:profile:convert` command) to perform the actual conversion.\n- **File System Scan:** It reads the contents of the `force-app/main/default/profiles` directory to identify all available Profile metadata files.\n- **Command Execution:** For each identified Profile (that is not excluded), it constructs and executes the `sf shane:profile:convert` command with the appropriate Profile name and desired Permission Set name.\n- **Error Handling:** Includes basic error handling for the external command execution.\n</details>\n",
+      "description": "Post notifications related to:\n\n- **Deployment simulation** _(use with --check-only)_\n\n- **Deployment process** _(to call only if your deployment is successful)_\n\n### Integrations\n\nAccording to the [integrations you configured](https://sfdx-hardis.cloudity.com/salesforce-ci-cd-setup-integrations-home/), notifications can contain deployment information and [Flow Visual Git Diff](https://sfdx-hardis.cloudity.com/salesforce-deployment-assistant-home/#flow-visual-git-diff)\n\n  - GitHub, Gitlab, Azure DevOps, Bitbucket comments on Pull Requests (including Flows Visual Git Diff)\n\n  - Slack, Microsoft Teams, Email deployment summary after a successful deployment\n\n  - JIRA tags and comments on tickets that just has been deployed\n\n![](https://sfdx-hardis.cloudity.com/assets/images/screenshot-jira-gitlab.jpg)\n\n![](https://sfdx-hardis.cloudity.com/assets/images/screenshot-jira-slack.jpg)\n\n### Flows Visual Git Diff\n\n- Visually show you the differences on a diagram\n\n- Display the update details without having to open any XML !\n\n🟩 = added\n\n🟥 = removed\n\n🟧 = updated\n\n![](https://sfdx-hardis.cloudity.com/assets/images/flow-visual-git-diff.jpg)\n\n![](https://sfdx-hardis.cloudity.com/assets/images/flow-visual-git-diff-2.jpg)\n\n### In custom CI/CD workflow\n\nExample of usage in a custom CI/CD pipeline:\n\n```bash\n# Disable exit-on-error temporarily\nset +e\n\n# Run the deploy command\nsf project deploy start [....]\nRET_CODE=$?\n\n# Re-enable exit-on-error\nset -e\n\n# Determine MYSTATUS based on return code\nif [ $RET_CODE -eq 0 ]; then\n    MYSTATUS=\"valid\"\nelse\n    MYSTATUS=\"invalid\"\nfi\n\n# Run the notify command with MYSTATUS\nsf hardis:project:deploy:notify --check-only --deploy-status \"$MYSTATUS\"\n```\n\n### Other usages\n\nThis command is for custom SF Cli pipelines, if you are a sfdx-hardis user, it is already embedded in sf hardis:deploy:smart.\n\nYou can also use [sfdx-hardis wrapper commands of SF deployment commands](https://sfdx-hardis.cloudity.com/salesforce-deployment-assistant-setup/#using-custom-cicd-pipeline)\n",
       "examples": [
-        "$ sf hardis:project:convert:profilestopermsets"
+        "$ sf hardis:project:deploy:notify --check-only --deploy-status valid --message \"This deployment check is valid\\n\\nYahooo !!\"",
+        "$ sf hardis:project:deploy:notify --check-only --deploy-status invalid --message \"This deployment check has failed !\\n\\Oh no !!\"",
+        "$ sf hardis:project:deploy:notify --deploy-status valid --message \"This deployment has been processed !\\n\\nYahooo !!\""
       ],
       "flags": {
         "json": {
@@ -11184,13 +11304,34 @@
           "multiple": false,
           "type": "option"
         },
-        "except": {
-          "char": "e",
-          "description": "List of filters",
-          "name": "except",
-          "default": [],
+        "check-only": {
+          "char": "c",
+          "description": "Use this option to send notifications from a Deployment simulation job",
+          "name": "check-only",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "deploy-status": {
+          "char": "s",
+          "description": "Send success, failure or unknown (default) to indicate if the deployment or deployment simulation is in success or not",
+          "name": "deploy-status",
+          "default": "unknown",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
+          "options": [
+            "valid",
+            "invalid",
+            "unknown"
+          ],
+          "type": "option"
+        },
+        "message": {
+          "char": "m",
+          "description": "Custom message that you want to be added in notifications (string or markdown format)",
+          "name": "message",
+          "default": "",
+          "hasDynamicHelp": false,
+          "multiple": false,
           "type": "option"
         },
         "debug": {
@@ -11212,65 +11353,76 @@
           "name": "skipauth",
           "allowNo": false,
           "type": "boolean"
+        },
+        "target-org": {
+          "aliases": [
+            "targetusername",
+            "u"
+          ],
+          "char": "o",
+          "deprecateAliases": true,
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "hardis:project:convert:profilestopermsets",
+      "id": "hardis:project:deploy:notify",
       "pluginAlias": "sfdx-hardis",
       "pluginName": "sfdx-hardis",
       "pluginType": "core",
       "strict": true,
       "enableJsonFlag": true,
-      "title": "Convert Profiles into Permission Sets",
+      "title": "Deployment Notifications",
       "requiresProject": true,
-      "requiresSfdxPlugins": [
-        "shane-sfdx-plugins"
-      ],
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "hardis",
         "project",
-        "convert",
-        "profilestopermsets.js"
+        "deploy",
+        "notify.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "hardis:project:convert:profilestopermsets",
-        "project:hardis:convert:profilestopermsets",
-        "project:convert:hardis:profilestopermsets",
-        "project:convert:profilestopermsets:hardis",
-        "hardis:convert:project:profilestopermsets",
-        "convert:hardis:project:profilestopermsets",
-        "convert:project:hardis:profilestopermsets",
-        "convert:project:profilestopermsets:hardis",
-        "hardis:convert:profilestopermsets:project",
-        "convert:hardis:profilestopermsets:project",
-        "convert:profilestopermsets:hardis:project",
-        "convert:profilestopermsets:project:hardis",
-        "hardis:project:profilestopermsets:convert",
-        "project:hardis:profilestopermsets:convert",
-        "project:profilestopermsets:hardis:convert",
-        "project:profilestopermsets:convert:hardis",
-        "hardis:profilestopermsets:project:convert",
-        "profilestopermsets:hardis:project:convert",
-        "profilestopermsets:project:hardis:convert",
-        "profilestopermsets:project:convert:hardis",
-        "hardis:profilestopermsets:convert:project",
-        "profilestopermsets:hardis:convert:project",
-        "profilestopermsets:convert:hardis:project",
-        "profilestopermsets:convert:project:hardis"
+        "hardis:project:deploy:notify",
+        "project:hardis:deploy:notify",
+        "project:deploy:hardis:notify",
+        "project:deploy:notify:hardis",
+        "hardis:deploy:project:notify",
+        "deploy:hardis:project:notify",
+        "deploy:project:hardis:notify",
+        "deploy:project:notify:hardis",
+        "hardis:deploy:notify:project",
+        "deploy:hardis:notify:project",
+        "deploy:notify:hardis:project",
+        "deploy:notify:project:hardis",
+        "hardis:project:notify:deploy",
+        "project:hardis:notify:deploy",
+        "project:notify:hardis:deploy",
+        "project:notify:deploy:hardis",
+        "hardis:notify:project:deploy",
+        "notify:hardis:project:deploy",
+        "notify:project:hardis:deploy",
+        "notify:project:deploy:hardis",
+        "hardis:notify:deploy:project",
+        "notify:hardis:deploy:project",
+        "notify:deploy:hardis:project",
+        "notify:deploy:project:hardis"
       ]
     },
-    "hardis:project:fix:profiletabs": {
-      "aliases": [],
-      "args": {},
-      "description": "\n## Command Behavior\n\n**Interactively updates tab visibility settings in Salesforce profiles, addressing a common issue where tab visibilities are not correctly retrieved by `sf project retrieve start`.**\n\nThis command provides a user-friendly interface to manage tab settings within your profile XML files, ensuring that your local project accurately reflects the intended tab configurations in your Salesforce org.\n\nKey functionalities:\n\n- **Interactive Tab Selection:** Displays a multi-select menu of all available tabs in your org, allowing you to choose which tabs to update.\n- **Visibility Control:** Lets you set the visibility for the selected tabs to either `DefaultOn` (Visible) or `Hidden`.\n- **Profile Selection:** Presents a multi-select menu of all .profile-meta.xml files in your project, allowing you to apply the tab visibility changes to specific profiles.\n- **XML Updates:** Modifies the <tabVisibilities> section of the selected profile XML files to reflect the chosen tab settings. If a tab visibility setting already exists for a selected tab, it will be updated; otherwise, a new one will be added.\n- **Sorted Output:** The <tabVisibilities> in the updated profile XML files are sorted alphabetically for consistency and readability.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **SOQL Queries (Tooling API):** It queries the `TabDefinition` object using `soqlQueryTooling` to retrieve a list of all available tabs in the target org.\n- **File Discovery:** Uses `glob` to find all .profile-meta.xml files within the specified project path.\n- **Interactive Prompts:** Leverages the `prompts` library to create interactive menus for selecting tabs, visibility settings, and profiles.\n- **XML Parsing and Manipulation:** Uses `parseXmlFile` to read the content of profile XML files and `writeXmlFile` to write the modified content back. It manipulates the `tabVisibilities` array within the parsed XML to add or update tab settings.\n- **Array Sorting:** Employs the `sort-array` library to sort the `tabVisibilities` alphabetically by tab name.\n- **Logging:** Provides feedback to the user about which profiles have been updated and a summary of the changes.\n</details>\n",
-      "examples": [
-        "$ sf hardis:project:fix:profiletabs"
+    "hardis:project:deploy:quick": {
+      "aliases": [
+        "hardis:deploy:quick"
       ],
+      "args": {},
+      "description": "sfdx-hardis wrapper for **sf project deploy quick** that displays tips to solve deployment errors.\n\nNote: Use **--json** argument to have better results\n\n[![Assisted solving of Salesforce deployments errors](https://github.com/hardisgroupcom/sfdx-hardis/raw/main/docs/assets/images/article-deployment-errors.jpg)](https://nicolas.vuillamy.fr/assisted-solving-of-salesforce-deployments-errors-47f3666a9ed0)\n\n[See documentation of Salesforce command](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_project_commands_unified.htm#cli_reference_project_deploy_quick_unified)\n\n### Deployment pre or post commands\n\nYou can define command lines to run before or after a deployment, with parameters:\n\n- **id**: Unique Id for the command\n- **label**: Human readable label for the command\n- **skipIfError**: If defined to \"true\", the post-command won't be run if there is a deployment failure\n- **context**: Defines the context where the command will be run. Can be **all** (default), **check-deployment-only** or **process-deployment-only**\n- **runOnlyOnceByOrg**: If set to true, the command will be run only one time per org. A record of SfdxHardisTrace__c is stored to make that possible (it needs to be existing in target org)\n\nIf the commands are not the same depending on the target org, you can define them into **config/branches/.sfdx-hardis-BRANCHNAME.yml** instead of root **config/.sfdx-hardis.yml**\n\nExample:\n\n```yaml\ncommandsPreDeploy:\n  - id: knowledgeUnassign\n    label: Remove KnowledgeUser right to the user who has it\n    command: sf data update record --sobject User --where \"UserPermissionsKnowledgeUser='true'\" --values \"UserPermissionsKnowledgeUser='false'\" --json\n  - id: knowledgeAssign\n    label: Assign Knowledge user to the deployment user\n    command: sf data update record --sobject User --where \"Username='deploy.github@myclient.com'\" --values \"UserPermissionsKnowledgeUser='true'\" --json\n\ncommandsPostDeploy:\n  - id: knowledgeUnassign\n    label: Remove KnowledgeUser right to the user who has it\n    command: sf data update record --sobject User --where \"UserPermissionsKnowledgeUser='true'\" --values \"UserPermissionsKnowledgeUser='false'\" --json\n  - id: knowledgeAssign\n    label: Assign Knowledge user to desired username\n    command: sf data update record --sobject User --where \"Username='admin-yser@myclient.com'\" --values \"UserPermissionsKnowledgeUser='true'\" --json\n  - id: someActionToRunJustOneTime\n    label: And to run only if deployment is success\n    command: sf sfdmu:run ...\n    skipIfError: true\n    context: process-deployment-only\n    runOnlyOnceByOrg: true\n```\n",
       "flags": {
         "json": {
           "description": "Format output as json.",
@@ -11287,372 +11439,20 @@
           "multiple": false,
           "type": "option"
         },
-        "path": {
-          "char": "p",
-          "description": "Root folder",
-          "name": "path",
-          "default": "/home/runner/work/sfdx-hardis/sfdx-hardis",
+        "api-version": {
+          "char": "a",
+          "description": "api-version",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "debug": {
-          "char": "d",
-          "description": "Activate debug mode (more logs)",
-          "name": "debug",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "websocket": {
-          "description": "Websocket host:port for VsCode SFDX Hardis UI integration",
-          "name": "websocket",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "skipauth": {
-          "description": "Skip authentication check when a default username is required",
-          "name": "skipauth",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "target-org": {
-          "aliases": [
-            "targetusername",
-            "u"
-          ],
-          "char": "o",
-          "deprecateAliases": true,
-          "name": "target-org",
-          "noCacheDefault": true,
-          "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
-          "hasDynamicHelp": true,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": true,
-      "hiddenAliases": [],
-      "id": "hardis:project:fix:profiletabs",
-      "pluginAlias": "sfdx-hardis",
-      "pluginName": "sfdx-hardis",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "title": "Fix profiles to add tabs that are not retrieved by SF CLI",
-      "requiresProject": true,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "hardis",
-        "project",
-        "fix",
-        "profiletabs.js"
-      ],
-      "aliasPermutations": [],
-      "permutations": [
-        "hardis:project:fix:profiletabs",
-        "project:hardis:fix:profiletabs",
-        "project:fix:hardis:profiletabs",
-        "project:fix:profiletabs:hardis",
-        "hardis:fix:project:profiletabs",
-        "fix:hardis:project:profiletabs",
-        "fix:project:hardis:profiletabs",
-        "fix:project:profiletabs:hardis",
-        "hardis:fix:profiletabs:project",
-        "fix:hardis:profiletabs:project",
-        "fix:profiletabs:hardis:project",
-        "fix:profiletabs:project:hardis",
-        "hardis:project:profiletabs:fix",
-        "project:hardis:profiletabs:fix",
-        "project:profiletabs:hardis:fix",
-        "project:profiletabs:fix:hardis",
-        "hardis:profiletabs:project:fix",
-        "profiletabs:hardis:project:fix",
-        "profiletabs:project:hardis:fix",
-        "profiletabs:project:fix:hardis",
-        "hardis:profiletabs:fix:project",
-        "profiletabs:hardis:fix:project",
-        "profiletabs:fix:hardis:project",
-        "profiletabs:fix:project:hardis"
-      ]
-    },
-    "hardis:project:fix:v53flexipages": {
-      "aliases": [],
-      "args": {},
-      "description": "\n## Command Behavior\n\n**Fixes Salesforce FlexiPages for compatibility with API Version 53.0 (Winter '22 release) by adding missing identifiers to component instances.**\n\nSalesforce introduced a change in API Version 53.0 that requires `identifier` tags within `componentInstance` and `fieldInstance` elements in FlexiPage metadata. If these identifiers are missing, deployments to orgs with API version 53.0 or higher will fail. This command automates the process of adding these missing identifiers, ensuring your FlexiPages remain deployable.\n\nKey functionalities:\n\n- **Targeted FlexiPage Processing:** Scans all .flexipage-meta.xml files within the specified root folder (defaults to current working directory).\n- **Identifier Injection:** Inserts a unique `identifier` tag (e.g., `SFDX_HARDIS_REPLACEMENT_ID`) into `componentInstance` and `fieldInstance` elements that lack one.\n\n**Important Note:** After running this command, ensure you update your `apiVersion` to `53.0` (or higher) in your `package.xml` and `sfdx-project.json` files.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **File Discovery:** Uses `glob` to find all .flexipage-meta.xml files.\n- **Content Reading:** Reads the XML content of each FlexiPage file.\n- **Regular Expression Replacement:** Employs a set of regular expressions to identify specific XML patterns (componentName.../componentName.../componentInstance, componentName.../componentName.../visibilityRule, fieldItem.../fieldItem.../fieldInstance) that are missing the `identifier` tag.\n- **Dynamic ID Generation:** For each match, it generates a unique identifier (e.g., `sfdxHardisIdX`) and injects it into the XML structure.\n- **File Writing:** If changes are made, the modified XML content is written back to the FlexiPage file using `fs.writeFile`.\n- **Logging:** Provides messages about which FlexiPages are being processed and a summary of the total number of identifiers added.\n</details>\n",
-      "examples": [
-        "$ sf hardis:project:fix:v53flexipages"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "flags-dir": {
-          "helpGroup": "GLOBAL",
-          "name": "flags-dir",
-          "summary": "Import flag values from a directory.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "path": {
-          "char": "p",
-          "description": "Root folder",
-          "name": "path",
-          "default": "/home/runner/work/sfdx-hardis/sfdx-hardis",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "debug": {
-          "char": "d",
-          "description": "Activate debug mode (more logs)",
-          "name": "debug",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "websocket": {
-          "description": "Websocket host:port for VsCode SFDX Hardis UI integration",
-          "name": "websocket",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "skipauth": {
-          "description": "Skip authentication check when a default username is required",
-          "name": "skipauth",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "hardis:project:fix:v53flexipages",
-      "pluginAlias": "sfdx-hardis",
-      "pluginName": "sfdx-hardis",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "title": "Fix flexipages for v53",
-      "requiresProject": true,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "hardis",
-        "project",
-        "fix",
-        "v53flexipages.js"
-      ],
-      "aliasPermutations": [],
-      "permutations": [
-        "hardis:project:fix:v53flexipages",
-        "project:hardis:fix:v53flexipages",
-        "project:fix:hardis:v53flexipages",
-        "project:fix:v53flexipages:hardis",
-        "hardis:fix:project:v53flexipages",
-        "fix:hardis:project:v53flexipages",
-        "fix:project:hardis:v53flexipages",
-        "fix:project:v53flexipages:hardis",
-        "hardis:fix:v53flexipages:project",
-        "fix:hardis:v53flexipages:project",
-        "fix:v53flexipages:hardis:project",
-        "fix:v53flexipages:project:hardis",
-        "hardis:project:v53flexipages:fix",
-        "project:hardis:v53flexipages:fix",
-        "project:v53flexipages:hardis:fix",
-        "project:v53flexipages:fix:hardis",
-        "hardis:v53flexipages:project:fix",
-        "v53flexipages:hardis:project:fix",
-        "v53flexipages:project:hardis:fix",
-        "v53flexipages:project:fix:hardis",
-        "hardis:v53flexipages:fix:project",
-        "v53flexipages:hardis:fix:project",
-        "v53flexipages:fix:hardis:project",
-        "v53flexipages:fix:project:hardis"
-      ]
-    },
-    "hardis:project:deploy:notify": {
-      "aliases": [],
-      "args": {},
-      "description": "Post notifications related to:\n\n- **Deployment simulation** _(use with --check-only)_\n\n- **Deployment process** _(to call only if your deployment is successful)_\n\n### Integrations\n\nAccording to the [integrations you configured](https://sfdx-hardis.cloudity.com/salesforce-ci-cd-setup-integrations-home/), notifications can contain deployment information and [Flow Visual Git Diff](https://sfdx-hardis.cloudity.com/salesforce-deployment-assistant-home/#flow-visual-git-diff)\n\n  - GitHub, Gitlab, Azure DevOps, Bitbucket comments on Pull Requests (including Flows Visual Git Diff)\n\n  - Slack, Microsoft Teams, Email deployment summary after a successful deployment\n\n  - JIRA tags and comments on tickets that just has been deployed\n\n![](https://sfdx-hardis.cloudity.com/assets/images/screenshot-jira-gitlab.jpg)\n\n![](https://sfdx-hardis.cloudity.com/assets/images/screenshot-jira-slack.jpg)\n\n### Flows Visual Git Diff\n\n- Visually show you the differences on a diagram\n\n- Display the update details without having to open any XML !\n\n🟩 = added\n\n🟥 = removed\n\n🟧 = updated\n\n![](https://sfdx-hardis.cloudity.com/assets/images/flow-visual-git-diff.jpg)\n\n![](https://sfdx-hardis.cloudity.com/assets/images/flow-visual-git-diff-2.jpg)\n\n### In custom CI/CD workflow\n\nExample of usage in a custom CI/CD pipeline:\n\n```bash\n# Disable exit-on-error temporarily\nset +e\n\n# Run the deploy command\nsf project deploy start [....]\nRET_CODE=$?\n\n# Re-enable exit-on-error\nset -e\n\n# Determine MYSTATUS based on return code\nif [ $RET_CODE -eq 0 ]; then\n    MYSTATUS=\"valid\"\nelse\n    MYSTATUS=\"invalid\"\nfi\n\n# Run the notify command with MYSTATUS\nsf hardis:project:deploy:notify --check-only --deploy-status \"$MYSTATUS\"\n```\n\n### Other usages\n\nThis command is for custom SF Cli pipelines, if you are a sfdx-hardis user, it is already embedded in sf hardis:deploy:smart.\n\nYou can also use [sfdx-hardis wrapper commands of SF deployment commands](https://sfdx-hardis.cloudity.com/salesforce-deployment-assistant-setup/#using-custom-cicd-pipeline)\n",
-      "examples": [
-        "$ sf hardis:project:deploy:notify --check-only --deploy-status valid --message \"This deployment check is valid\\n\\nYahooo !!\"",
-        "$ sf hardis:project:deploy:notify --check-only --deploy-status invalid --message \"This deployment check has failed !\\n\\Oh no !!\"",
-        "$ sf hardis:project:deploy:notify --deploy-status valid --message \"This deployment has been processed !\\n\\nYahooo !!\""
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "flags-dir": {
-          "helpGroup": "GLOBAL",
-          "name": "flags-dir",
-          "summary": "Import flag values from a directory.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "check-only": {
-          "char": "c",
-          "description": "Use this option to send notifications from a Deployment simulation job",
-          "name": "check-only",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "deploy-status": {
-          "char": "s",
-          "description": "Send success, failure or unknown (default) to indicate if the deployment or deployment simulation is in success or not",
-          "name": "deploy-status",
-          "default": "unknown",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "valid",
-            "invalid",
-            "unknown"
-          ],
-          "type": "option"
-        },
-        "message": {
-          "char": "m",
-          "description": "Custom message that you want to be added in notifications (string or markdown format)",
-          "name": "message",
-          "default": "",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "debug": {
-          "char": "d",
-          "description": "Activate debug mode (more logs)",
-          "name": "debug",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "websocket": {
-          "description": "Websocket host:port for VsCode SFDX Hardis UI integration",
-          "name": "websocket",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "skipauth": {
-          "description": "Skip authentication check when a default username is required",
-          "name": "skipauth",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "target-org": {
-          "aliases": [
-            "targetusername",
-            "u"
-          ],
-          "char": "o",
-          "deprecateAliases": true,
-          "name": "target-org",
-          "noCacheDefault": true,
-          "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
-          "hasDynamicHelp": true,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": true,
-      "hiddenAliases": [],
-      "id": "hardis:project:deploy:notify",
-      "pluginAlias": "sfdx-hardis",
-      "pluginName": "sfdx-hardis",
-      "pluginType": "core",
-      "strict": true,
-      "enableJsonFlag": true,
-      "title": "Deployment Notifications",
-      "requiresProject": true,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "hardis",
-        "project",
-        "deploy",
-        "notify.js"
-      ],
-      "aliasPermutations": [],
-      "permutations": [
-        "hardis:project:deploy:notify",
-        "project:hardis:deploy:notify",
-        "project:deploy:hardis:notify",
-        "project:deploy:notify:hardis",
-        "hardis:deploy:project:notify",
-        "deploy:hardis:project:notify",
-        "deploy:project:hardis:notify",
-        "deploy:project:notify:hardis",
-        "hardis:deploy:notify:project",
-        "deploy:hardis:notify:project",
-        "deploy:notify:hardis:project",
-        "deploy:notify:project:hardis",
-        "hardis:project:notify:deploy",
-        "project:hardis:notify:deploy",
-        "project:notify:hardis:deploy",
-        "project:notify:deploy:hardis",
-        "hardis:notify:project:deploy",
-        "notify:hardis:project:deploy",
-        "notify:project:hardis:deploy",
-        "notify:project:deploy:hardis",
-        "hardis:notify:deploy:project",
-        "notify:hardis:deploy:project",
-        "notify:deploy:hardis:project",
-        "notify:deploy:project:hardis"
-      ]
-    },
-    "hardis:project:deploy:quick": {
-      "aliases": [
-        "hardis:deploy:quick"
-      ],
-      "args": {},
-      "description": "sfdx-hardis wrapper for **sf project deploy quick** that displays tips to solve deployment errors.\n\nNote: Use **--json** argument to have better results\n\n[![Assisted solving of Salesforce deployments errors](https://github.com/hardisgroupcom/sfdx-hardis/raw/main/docs/assets/images/article-deployment-errors.jpg)](https://nicolas.vuillamy.fr/assisted-solving-of-salesforce-deployments-errors-47f3666a9ed0)\n\n[See documentation of Salesforce command](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_project_commands_unified.htm#cli_reference_project_deploy_quick_unified)\n\n### Deployment pre or post commands\n\nYou can define command lines to run before or after a deployment, with parameters:\n\n- **id**: Unique Id for the command\n- **label**: Human readable label for the command\n- **skipIfError**: If defined to \"true\", the post-command won't be run if there is a deployment failure\n- **context**: Defines the context where the command will be run. Can be **all** (default), **check-deployment-only** or **process-deployment-only**\n- **runOnlyOnceByOrg**: If set to true, the command will be run only one time per org. A record of SfdxHardisTrace__c is stored to make that possible (it needs to be existing in target org)\n\nIf the commands are not the same depending on the target org, you can define them into **config/branches/.sfdx-hardis-BRANCHNAME.yml** instead of root **config/.sfdx-hardis.yml**\n\nExample:\n\n```yaml\ncommandsPreDeploy:\n  - id: knowledgeUnassign\n    label: Remove KnowledgeUser right to the user who has it\n    command: sf data update record --sobject User --where \"UserPermissionsKnowledgeUser='true'\" --values \"UserPermissionsKnowledgeUser='false'\" --json\n  - id: knowledgeAssign\n    label: Assign Knowledge user to the deployment user\n    command: sf data update record --sobject User --where \"Username='deploy.github@myclient.com'\" --values \"UserPermissionsKnowledgeUser='true'\" --json\n\ncommandsPostDeploy:\n  - id: knowledgeUnassign\n    label: Remove KnowledgeUser right to the user who has it\n    command: sf data update record --sobject User --where \"UserPermissionsKnowledgeUser='true'\" --values \"UserPermissionsKnowledgeUser='false'\" --json\n  - id: knowledgeAssign\n    label: Assign Knowledge user to desired username\n    command: sf data update record --sobject User --where \"Username='admin-yser@myclient.com'\" --values \"UserPermissionsKnowledgeUser='true'\" --json\n  - id: someActionToRunJustOneTime\n    label: And to run only if deployment is success\n    command: sf sfdmu:run ...\n    skipIfError: true\n    context: process-deployment-only\n    runOnlyOnceByOrg: true\n```\n",
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "flags-dir": {
-          "helpGroup": "GLOBAL",
-          "name": "flags-dir",
-          "summary": "Import flag values from a directory.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "api-version": {
-          "char": "a",
-          "description": "api-version",
-          "name": "api-version",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "async": {
-          "description": "async",
-          "exclusive": [
-            "wait"
-          ],
-          "name": "async",
+        "async": {
+          "description": "async",
+          "exclusive": [
+            "wait"
+          ],
+          "name": "async",
           "allowNo": false,
           "type": "boolean"
         },
@@ -12654,6 +12454,221 @@
         "validate:deploy:project:hardis"
       ]
     },
+    "hardis:project:fix:profiletabs": {
+      "aliases": [],
+      "args": {},
+      "description": "\n## Command Behavior\n\n**Interactively updates tab visibility settings in Salesforce profiles, addressing a common issue where tab visibilities are not correctly retrieved by `sf project retrieve start`.**\n\nThis command provides a user-friendly interface to manage tab settings within your profile XML files, ensuring that your local project accurately reflects the intended tab configurations in your Salesforce org.\n\nKey functionalities:\n\n- **Interactive Tab Selection:** Displays a multi-select menu of all available tabs in your org, allowing you to choose which tabs to update.\n- **Visibility Control:** Lets you set the visibility for the selected tabs to either `DefaultOn` (Visible) or `Hidden`.\n- **Profile Selection:** Presents a multi-select menu of all .profile-meta.xml files in your project, allowing you to apply the tab visibility changes to specific profiles.\n- **XML Updates:** Modifies the <tabVisibilities> section of the selected profile XML files to reflect the chosen tab settings. If a tab visibility setting already exists for a selected tab, it will be updated; otherwise, a new one will be added.\n- **Sorted Output:** The <tabVisibilities> in the updated profile XML files are sorted alphabetically for consistency and readability.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **SOQL Queries (Tooling API):** It queries the `TabDefinition` object using `soqlQueryTooling` to retrieve a list of all available tabs in the target org.\n- **File Discovery:** Uses `glob` to find all .profile-meta.xml files within the specified project path.\n- **Interactive Prompts:** Leverages the `prompts` library to create interactive menus for selecting tabs, visibility settings, and profiles.\n- **XML Parsing and Manipulation:** Uses `parseXmlFile` to read the content of profile XML files and `writeXmlFile` to write the modified content back. It manipulates the `tabVisibilities` array within the parsed XML to add or update tab settings.\n- **Array Sorting:** Employs the `sort-array` library to sort the `tabVisibilities` alphabetically by tab name.\n- **Logging:** Provides feedback to the user about which profiles have been updated and a summary of the changes.\n</details>\n",
+      "examples": [
+        "$ sf hardis:project:fix:profiletabs"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "path": {
+          "char": "p",
+          "description": "Root folder",
+          "name": "path",
+          "default": "/home/runner/work/sfdx-hardis/sfdx-hardis",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "debug": {
+          "char": "d",
+          "description": "Activate debug mode (more logs)",
+          "name": "debug",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "websocket": {
+          "description": "Websocket host:port for VsCode SFDX Hardis UI integration",
+          "name": "websocket",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "skipauth": {
+          "description": "Skip authentication check when a default username is required",
+          "name": "skipauth",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "target-org": {
+          "aliases": [
+            "targetusername",
+            "u"
+          ],
+          "char": "o",
+          "deprecateAliases": true,
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "hardis:project:fix:profiletabs",
+      "pluginAlias": "sfdx-hardis",
+      "pluginName": "sfdx-hardis",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "title": "Fix profiles to add tabs that are not retrieved by SF CLI",
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "hardis",
+        "project",
+        "fix",
+        "profiletabs.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "hardis:project:fix:profiletabs",
+        "project:hardis:fix:profiletabs",
+        "project:fix:hardis:profiletabs",
+        "project:fix:profiletabs:hardis",
+        "hardis:fix:project:profiletabs",
+        "fix:hardis:project:profiletabs",
+        "fix:project:hardis:profiletabs",
+        "fix:project:profiletabs:hardis",
+        "hardis:fix:profiletabs:project",
+        "fix:hardis:profiletabs:project",
+        "fix:profiletabs:hardis:project",
+        "fix:profiletabs:project:hardis",
+        "hardis:project:profiletabs:fix",
+        "project:hardis:profiletabs:fix",
+        "project:profiletabs:hardis:fix",
+        "project:profiletabs:fix:hardis",
+        "hardis:profiletabs:project:fix",
+        "profiletabs:hardis:project:fix",
+        "profiletabs:project:hardis:fix",
+        "profiletabs:project:fix:hardis",
+        "hardis:profiletabs:fix:project",
+        "profiletabs:hardis:fix:project",
+        "profiletabs:fix:hardis:project",
+        "profiletabs:fix:project:hardis"
+      ]
+    },
+    "hardis:project:fix:v53flexipages": {
+      "aliases": [],
+      "args": {},
+      "description": "\n## Command Behavior\n\n**Fixes Salesforce FlexiPages for compatibility with API Version 53.0 (Winter '22 release) by adding missing identifiers to component instances.**\n\nSalesforce introduced a change in API Version 53.0 that requires `identifier` tags within `componentInstance` and `fieldInstance` elements in FlexiPage metadata. If these identifiers are missing, deployments to orgs with API version 53.0 or higher will fail. This command automates the process of adding these missing identifiers, ensuring your FlexiPages remain deployable.\n\nKey functionalities:\n\n- **Targeted FlexiPage Processing:** Scans all .flexipage-meta.xml files within the specified root folder (defaults to current working directory).\n- **Identifier Injection:** Inserts a unique `identifier` tag (e.g., `SFDX_HARDIS_REPLACEMENT_ID`) into `componentInstance` and `fieldInstance` elements that lack one.\n\n**Important Note:** After running this command, ensure you update your `apiVersion` to `53.0` (or higher) in your `package.xml` and `sfdx-project.json` files.\n\n<details markdown=\"1\">\n<summary>Technical explanations</summary>\n\nThe command's technical implementation involves:\n\n- **File Discovery:** Uses `glob` to find all .flexipage-meta.xml files.\n- **Content Reading:** Reads the XML content of each FlexiPage file.\n- **Regular Expression Replacement:** Employs a set of regular expressions to identify specific XML patterns (componentName.../componentName.../componentInstance, componentName.../componentName.../visibilityRule, fieldItem.../fieldItem.../fieldInstance) that are missing the `identifier` tag.\n- **Dynamic ID Generation:** For each match, it generates a unique identifier (e.g., `sfdxHardisIdX`) and injects it into the XML structure.\n- **File Writing:** If changes are made, the modified XML content is written back to the FlexiPage file using `fs.writeFile`.\n- **Logging:** Provides messages about which FlexiPages are being processed and a summary of the total number of identifiers added.\n</details>\n",
+      "examples": [
+        "$ sf hardis:project:fix:v53flexipages"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "path": {
+          "char": "p",
+          "description": "Root folder",
+          "name": "path",
+          "default": "/home/runner/work/sfdx-hardis/sfdx-hardis",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "debug": {
+          "char": "d",
+          "description": "Activate debug mode (more logs)",
+          "name": "debug",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "websocket": {
+          "description": "Websocket host:port for VsCode SFDX Hardis UI integration",
+          "name": "websocket",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "skipauth": {
+          "description": "Skip authentication check when a default username is required",
+          "name": "skipauth",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "hardis:project:fix:v53flexipages",
+      "pluginAlias": "sfdx-hardis",
+      "pluginName": "sfdx-hardis",
+      "pluginType": "core",
+      "strict": true,
+      "enableJsonFlag": true,
+      "title": "Fix flexipages for v53",
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "hardis",
+        "project",
+        "fix",
+        "v53flexipages.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "hardis:project:fix:v53flexipages",
+        "project:hardis:fix:v53flexipages",
+        "project:fix:hardis:v53flexipages",
+        "project:fix:v53flexipages:hardis",
+        "hardis:fix:project:v53flexipages",
+        "fix:hardis:project:v53flexipages",
+        "fix:project:hardis:v53flexipages",
+        "fix:project:v53flexipages:hardis",
+        "hardis:fix:v53flexipages:project",
+        "fix:hardis:v53flexipages:project",
+        "fix:v53flexipages:hardis:project",
+        "fix:v53flexipages:project:hardis",
+        "hardis:project:v53flexipages:fix",
+        "project:hardis:v53flexipages:fix",
+        "project:v53flexipages:hardis:fix",
+        "project:v53flexipages:fix:hardis",
+        "hardis:v53flexipages:project:fix",
+        "v53flexipages:hardis:project:fix",
+        "v53flexipages:project:hardis:fix",
+        "v53flexipages:project:fix:hardis",
+        "hardis:v53flexipages:fix:project",
+        "v53flexipages:hardis:fix:project",
+        "v53flexipages:fix:hardis:project",
+        "v53flexipages:fix:project:hardis"
+      ]
+    },
     "hardis:project:generate:bypass": {
       "aliases": [],
       "args": {},
@@ -15136,5 +15151,5 @@
       ]
     }
   },
-  "version": "6.1.5-beta202508282306.0"
+  "version": "6.2.1"
 }