refactor: Update CLI commands to use 'penify' instead of 'penifycli' for consistency across documentation

Author: sumansaurabh

.vitepress/config.mts

@@ -125,10 +125,6 @@ export default defineConfig({
           },
         ],
       }]},
-      {items: [{
-        text: "💰 Penify Pricing",
-        link: "/docs/penify-pricing.md",
-      }]},
       {
         items: [{
         text: "💠 Penify Dashboard",
@@ -160,17 +156,19 @@ export default defineConfig({
           text: "🖥️ Penify CLI",
           link: "/docs/penify-cli",
           items:[{
-            text: "📝 Detailed Usage guide",
+            text: "📝 Usage guide",
             link: "/docs/penify-cli-detailed-usage",
+            collapsed: true,
+            items: [
+              {
+                text: "🔑 Create API Keys",
+                link: "/docs/Creating-API-Keys-in-Penify",
+              }]
           },
           {
-            text: "🔑 Create API Token",
-            link: "/docs/Creating-API-Keys-in-Penify",
-          },
-          {
-            text: "📝 Configure LLM + JIRA",
-            link: "/docs/config-cli-documentation",
-            collapsed: true,
+            text: "📝 Configure Setup",
+            link: "/docs/config-cli-documentation#llm-configuration",
+            collapsed: false,
             items: [
               {
                 text: "📝 Local LLM",
@@ -179,6 +177,10 @@ export default defineConfig({
               {
                 text: "📝 Jira",
                 link: "/docs/config-cli-documentation#using-local-llm#jira-configuration",
+              },
+              {
+                text: "📝 Commit Hooks",
+                link: "/docs/post-commit-hooks-cli",
               }]
           },
           {
@@ -207,14 +209,14 @@ export default defineConfig({
           {
             text: "📝 Commit Documentation",
             link: "/docs/commit-documentation-cli",
-          },
-          {
-            text: "📝 Post-Commit Hooks",
-            link: "/docs/post-commit-hooks-cli",
           }]
           }
         ],
       },
+      {items: [{
+        text: "💰 Penify Pricing",
+        link: "/docs/penify-pricing.md",
+      }]},
     ],
 
     socialLinks: [

docs/commit-documentation-cli.md

@@ -16,7 +16,7 @@ Penify-CLI can generate documentation of classes/functions for your recent chang
 Login to Penify, make sure you have an account or you have [created an account](https://www.penify.dev/).
 
 ```bash
-penifycli login
+penify login
 ```
 
 ## Usage
@@ -25,7 +25,7 @@ To document recent Git changes:
 
 ```bash
 cd /path/to/folder
-penifycli doc-gen
+penify doc-gen
 ```
 
 ### Options

docs/commit-summary-generation-cli.md

@@ -15,7 +15,7 @@ The `commit` command allows you to generate smart, AI-powered commit messages fo
 ## Basic Usage
 
 ```bash
-penifycli commit
+penify commit
 ```
 
 By default, this command:
@@ -30,7 +30,7 @@ By default, this command:
 Provide context for the commit message generation:
 
 ```bash
-penifycli commit -m "Fix login flow"
+penify commit -m "Fix login flow"
 ```
 
 This hint helps the AI understand your intention and improves the quality of the generated message.
@@ -40,7 +40,7 @@ This hint helps the AI understand your intention and improves the quality of the
 Open an editor to review and edit the generated commit message before committing:
 
 ```bash
-penifycli commit -e
+penify commit -e
 ```
 
 This opens your default Git editor with the generated message for review.
@@ -50,7 +50,7 @@ This opens your default Git editor with the generated message for review.
 Generate a detailed commit message with both title and description:
 
 ```bash
-penifycli commit -d
+penify commit -d
 ```
 
 Without this flag, only the commit title is generated.
@@ -62,32 +62,32 @@ You can combine these options for different workflows:
 ### Generate Title Only with Context
 
 ```bash
-penifycli commit -m "Update login UI"
+penify commit -m "Update login UI"
 ```
 
 ### Generate Title and Description with Context
 
 ```bash
-penifycli commit -m "Update login UI" -d
+penify commit -m "Update login UI" -d
 ```
 
 ### Generate and Edit Full Commit Message
 
 ```bash
-penifycli commit -d -e
+penify commit -d -e
 ```
 
 ### Generate, Edit, and Provide Context
 
 ```bash
-penifycli commit -m "Refactor authentication" -d -e
+penify commit -m "Refactor authentication" -d -e
 ```
 
 ## LLM and JIRA Integration
 
 ### Using Local LLM
 
-If you've configured a local LLM using `penifycli config llm`, the commit command will automatically use it for message generation.
+If you've configured a local LLM using `penify config llm`, the commit command will automatically use it for message generation.
 
 Benefits:
 - Privacy: your code changes don't leave your machine
@@ -96,7 +96,7 @@ Benefits:
 
 ### JIRA Enhancement
 
-If you've configured JIRA integration using `penifycli config jira`, the commit command will:
+If you've configured JIRA integration using `penify config jira`, the commit command will:
 
 1. Detect JIRA issue references in your changes
 2. Fetch issue details from your JIRA instance
@@ -119,11 +119,11 @@ PROJ-123: Fix authentication bug in login flow
 For the `commit` command to work:
 
 1. You must have configured either:
-   - Local LLM via `penifycli config llm`, OR
-   - Logged in via `penifycli login`
+   - Local LLM via `penify config llm`, OR
+   - Logged in via `penify login`
 
 2. For JIRA enhancement (optional):
-   - Configure JIRA via `penifycli config jira`
+   - Configure JIRA via `penify config jira`
 
 ## Examples
 
@@ -134,7 +134,7 @@ For the `commit` command to work:
 git add .
 
 # Generate commit message
-penifycli commit
+penify commit
 
 # Commit with the generated message
 git commit -m "Generated message here"
@@ -148,7 +148,7 @@ git add .
 
 # Generate detailed commit message with JIRA integration, 
 # provide context, and open editor for review
-penifycli commit -m "Fix login issue" -d -e
+penify commit -m "Fix login issue" -d -e
 
 # The commit is automatically completed after you save and exit the editor
 ```
@@ -158,8 +158,8 @@ penifycli commit -m "Fix login issue" -d -e
 ### Common Issues
 
 1. **"No LLM model or API token provided"**
-   - Run `penifycli config llm` to configure a local LLM, or
-   - Run `penifycli login` to authenticate with Penify
+   - Run `penify config llm` to configure a local LLM, or
+   - Run `penify login` to authenticate with Penify
 
 2. **"Failed to connect to JIRA"**
    - Check your JIRA configuration with `cat ~/.penify`

docs/config-cli-documentation.md

@@ -24,17 +24,17 @@ Penify CLI stores configuration in a JSON file at `~/.penify/config.json`. The c
 
 ```bash
 # Configure LLM settings
-penifycli config llm
+penify config llm
 
 # Configure JIRA integration
-penifycli config jira
+penify config jira
 ```
 
 ## LLM Configuration
 
 ### Web Interface
 
-Running `penifycli config llm` opens a web interface in your browser where you can configure:
+Running `penify config llm` opens a web interface in your browser where you can configure:
 
 1. **Model**: The LLM model to use (e.g., `gpt-3.5-turbo`)
 2. **API Base URL**: The endpoint URL for your LLM API (e.g., `https://api.openai.com/v1`)
@@ -82,7 +82,7 @@ After configuration, your `~/.penify/config.json` will contain:
 
 ### Web Interface
 
-Running `penifycli config jira` opens a web interface where you can configure:
+Running `penify config jira` opens a web interface where you can configure:
 
 1. **JIRA URL**: Your JIRA instance URL (e.g., `https://yourcompany.atlassian.net`)
 2. **Username**: Your JIRA username (typically your email)
@@ -133,7 +133,7 @@ You can override configuration settings using environment variables:
 Example:
 ```bash
 export PENIFY_LLM_MODEL="gpt-4"
-penifycli commit
+penify commit
 ```
 
 ## Command-Line Configuration

docs/file-documentation-cli.md

@@ -17,15 +17,15 @@ Penify-CLI can generate comprehensive documentation for individual code files.
 Login to Penify, make sure you have an account or you have [created an account](https://www.penify.dev/).
 
 ```bash
-penifycli login
+penify login
 ```
 
 ## Usage
 
 To generate documentation for a single file:
 
 ```bash
-penifycli doc-gen -fl /path/to/your/file.py
+penify doc-gen -fl /path/to/your/file.py
 ```
 
 ### Options
@@ -36,7 +36,7 @@ penifycli doc-gen -fl /path/to/your/file.py
 ## Example
 
 ```bash
-penifycli doc-gen -fl /path/to/project/main.py
+penify doc-gen -fl /path/to/project/main.py
 ```
 
 ## Output

docs/git-commit-guide.md

@@ -55,7 +55,7 @@ Use the following structure for your commit messages:
 Penify-CLI can help generate comprehensive commit messages:
 
 ```bash
-penifycli commit -gf /path/to/repo -t your_token
+penify commit -gf /path/to/repo -t your_token
 ```
 
 This command will analyze your changes and generate a commit message. You can then review and edit if necessary.
@@ -127,7 +127,7 @@ Fixes #456
 Penify-CLI can help analyze your commits and suggest improvements:
 
 ```bash
-penifycli analyze-commits -gf /path/to/repo -t your_token
+penify analyze-commits -gf /path/to/repo -t your_token
 ```
 
 This command will provide feedback on your recent commits and suggest ways to improve them.

docs/git-workflow-guide.md

@@ -28,7 +28,7 @@ This guide outlines best practices for managing and documenting changes in your
 1. **Commit Often**: Make small, focused commits rather than large, multi-purpose ones.
 2. **Write Clear Commit Messages**: Use Penify-CLI's commit summary generation for consistency.
    ```bash
-   penifycli commit -gf /path/to/repo -t your_token
+   penify commit -gf /path/to/repo -t your_token
    ```
 3. **Use Conventional Commit Messages**: Follow a format like:
    ```
@@ -45,7 +45,7 @@ This guide outlines best practices for managing and documenting changes in your
 1. Create a Pull Request (PR) for your feature branch.
 2. Use Penify-CLI to generate documentation for changed files:
    ```bash
-   penifycli doc-gen -t your_token -gf /path/to/repo
+   penify doc-gen -t your_token -gf /path/to/repo
    ```
 3. Include generated documentation in your PR description.
 4. Assign reviewers and address their comments.
@@ -57,15 +57,15 @@ This guide outlines best practices for managing and documenting changes in your
 2. **Keep README.md Current**: Update project overview and setup instructions as needed.
 3. **In-Code Documentation**: Use Penify-CLI to generate and update docstrings:
    ```bash
-   penifycli doc-gen -t your_token -fl /path/to/file.py
+   penify doc-gen -t your_token -fl /path/to/file.py
    ```
 
 ## 5. Release Process
 
 1. Create a release branch from `develop`.
 2. Use Penify-CLI to generate full repository documentation:
    ```bash
-   penifycli doc-gen -t your_token -cf /path/to/repo
+   penify doc-gen -t your_token -cf /path/to/repo
    ```
 3. Update version numbers and CHANGELOG.md.
 4. Merge release branch to `main` and tag the release.

docs/instant-pull-request-insight.md

@@ -455,7 +455,7 @@ Penify's LLM implements self-reflection to improve result quality:
 ### Command Line Interface
 
 ```bash
-penifycli pr insight --pr-number 123 --command review
+penify pr insight --pr-number 123 --command review
 ```
 
 ### GitHub App / Webhook

docs/instant-pull-request-insigt.md

@@ -441,7 +441,7 @@ Penify's AI implements self-reflection to improve result quality:
 ### Command Line Interface
 
 ```bash
-penifycli pr insight --repo-path /path/to/repo --pr-number 123 --command review
+penify pr insight --repo-path /path/to/repo --pr-number 123 --command review
 ```
 
 ### GitHub App / Webhook