Feat/rename cli packmind

.claude/skills/doc-audit/SKILL.md

@@ -112,7 +112,7 @@ Generated: {date} | Pages audited: {count}
 [... more findings]
 
 ### [B] Outdated CLI Commands
-- **{page}** (line ~{N}): References `packmind-cli {cmd}` — command not found in CLI source
+- **{page}** (line ~{N}): References `packmind {cmd}` — command not found in CLI source
 [... more findings]
 
 ### [C] Non-Existent Concepts

.claude/skills/doc-audit/references/section-audit-instructions.md

@@ -27,13 +27,13 @@ You are auditing a section of the Packmind end-user documentation. Your job is t
 
 ### Category B: Outdated CLI Commands (ERROR)
 
-**What to check:** References to `packmind-cli <command>` or CLI command names in the documentation.
+**What to check:** References to `packmind <command>` or CLI command names in the documentation.
 
 **How to verify:** Start with the CLI commands ground truth list, then **read the actual command source file** to verify. Command files follow the pattern `*Command.ts` or `*Handler.ts` in `apps/cli/src/infra/commands/`. When a doc references a specific command, open the corresponding source file to confirm the command name, subcommands, and described behavior match.
 
 **Valid finding:**
-- Doc references `packmind-cli migrate` but no `MigrateCommand.ts` or `migrateHandler.ts` exists in CLI source
-- Doc says `packmind-cli lint --fix` supports auto-fix but reading `LintCommand.ts` shows no `--fix` option
+- Doc references `packmind migrate` but no `MigrateCommand.ts` or `migrateHandler.ts` exists in CLI source
+- Doc says `packmind lint --fix` supports auto-fix but reading `LintCommand.ts` shows no `--fix` option
 
 **Not a finding (false positive):**
 - CLI flags or options that DO exist in the source when you read the file
@@ -104,7 +104,7 @@ Where:
 
 ```
 [ERROR] [A] **getting-started/gs-onboarding.mdx** (line ~45): Link to `/concepts/workflow-management` — no matching MDX file exists in apps/doc/concepts/
-[ERROR] [B] **tools/cli.mdx** (line ~120): References `packmind-cli migrate` — no MigrateCommand.ts found in CLI source
+[ERROR] [B] **tools/cli.mdx** (line ~120): References `packmind migrate` — no MigrateCommand.ts found in CLI source
 [ERROR] [D] **concepts/standards-management.mdx** (line ~30): "Coming in Q2 2024" — date has passed (current date: 2026-03-12)
 [WARNING] [E] **N/A**: CLI command `SyncCommand.ts` has no documentation coverage
 ```

.claude/skills/packmind-create-command/README.md

@@ -29,8 +29,8 @@ The AI agent will:
 
 Before using this skill, ensure you have:
 
-- **packmind-cli**: Required for command creation
-- **Packmind account**: Login via `packmind-cli login`
+- **packmind**: Required for command creation
+- **Packmind account**: Login via `packmind login`
 
 ## License
 

.claude/skills/packmind-create-command/SKILL.md

@@ -86,12 +86,12 @@ The CLI validates the command after conversion. Ensure the markdown file meets t
 
 ## Prerequisites
 
-Before creating a command, verify that packmind-cli is available:
+Before creating a command, verify that packmind is available:
 
-Check if packmind-cli is installed:
+Check if packmind is installed:
 
 ```bash
-packmind-cli --version
+packmind --version
 ```
 
 If not available, install it:
@@ -103,7 +103,7 @@ npm install -g @packmind/cli
 Then login to Packmind:
 
 ```bash
-packmind-cli login
+packmind login
 ```
 
 ## Command Creation Process
@@ -222,22 +222,22 @@ Define specific, actionable scenarios:
 6. Pipe the JSON directly to the CLI via stdin using a heredoc (no intermediate file needed):
 
 ```bash
-packmind-cli commands create --origin-skill packmind-create-command <<'EOF'
+packmind commands create --origin-skill packmind-create-command <<'EOF'
 {"name":"...","summary":"...","whenToUse":[...],"contextValidationCheckpoints":[...],"steps":[...]}
 EOF
 ```
 
 Expected output on success:
 ```
-packmind-cli Command "Your Command Name" created successfully (ID: <uuid>)
+packmind Command "Your Command Name" created successfully (ID: <uuid>)
 View it in the webapp: <url>
 ```
 
 #### Troubleshooting
 
 **"Not logged in" error:**
 ```bash
-packmind-cli login
+packmind login
 ```
 
 **"Failed to resolve global space" error:**
@@ -259,7 +259,7 @@ After the command is **successfully created**, delete the draft markdown file in
 
 After successful creation, check if the command fits an existing package:
 
-1. Run `packmind-cli install --list` to get available packages
+1. Run `packmind install --list` to get available packages
 2. If no packages exist, skip this step silently and end the workflow
 3. Analyze the created command's name and summary against each package's name and description
 4. If a package is a clear semantic fit (the command's domain/technology aligns with the package's purpose):
@@ -270,9 +270,9 @@ After successful creation, check if the command fits an existing package:
      - Skip
 5. If no clear fit is found, skip silently (do not mention packages)
 6. If user chooses to add:
-   - Run: `packmind-cli packages add --to <package-slug> --command <command-slug>`
-   - Ask: "Would you like me to run `packmind-cli install` to sync the changes?"
-   - If yes, run: `packmind-cli install`
+   - Run: `packmind packages add --to <package-slug> --command <command-slug>`
+   - Ask: "Would you like me to run `packmind install` to sync the changes?"
+   - If yes, run: `packmind install`
 
 ## Complete Example
 
@@ -328,7 +328,7 @@ Add the controller and use case to the appropriate NestJS module's \`controllers
 
 **Creating the command (piped via stdin):**
 ```bash
-packmind-cli commands create --origin-skill packmind-create-command <<'EOF'
+packmind commands create --origin-skill packmind-create-command <<'EOF'
 {"name":"Create API Endpoint","summary":"Set up a new REST API endpoint...","whenToUse":[...],"contextValidationCheckpoints":[...],"steps":[...]}
 EOF
 ```

.claude/skills/packmind-create-package/README.md

@@ -26,8 +26,8 @@ The AI agent will:
 
 Before using this skill, ensure you have:
 
-- **packmind-cli**: Required for package creation
-- **Packmind account**: Login via `packmind-cli login`
+- **packmind**: Required for package creation
+- **Packmind account**: Login via `packmind login`
 
 ## License
 

.claude/skills/packmind-create-package/SKILL.md

@@ -16,17 +16,17 @@ Examples: `frontend`, `backend-api`, `nestjs`, `e2e`
 
 ## Prerequisites
 
-Verify packmind-cli is available:
+Verify packmind is available:
 
 ```bash
-packmind-cli --version
+packmind --version
 ```
 
 If not installed:
 
 ```bash
 npm install -g @packmind/cli
-packmind-cli login
+packmind login
 ```
 
 ## Workflow
@@ -36,7 +36,7 @@ packmind-cli login
 List existing packages to identify naming conventions:
 
 ```bash
-packmind-cli install --list
+packmind install --list
 ```
 
 Review the output to:
@@ -62,13 +62,13 @@ Wait for explicit user approval.
 Run the CLI command:
 
 ```bash
-packmind-cli packages create "<name>" --description="<description>"
+packmind packages create "<name>" --description="<description>"
 ```
 
 Or without description:
 
 ```bash
-packmind-cli packages create "<name>"
+packmind packages create "<name>"
 ```
 
 ### Expected Output
@@ -78,7 +78,7 @@ On success:
 ```
 Created: <slug>
 You can see it at: https://<host>/packages/<slug>
-You can install it with: packmind-cli packages install <slug>
+You can install it with: packmind packages install <slug>
 ```
 
 ## Naming Guidelines
@@ -91,7 +91,7 @@ You can install it with: packmind-cli packages install <slug>
 
 | Error | Solution |
 |-------|----------|
-| "Not authenticated" | Run `packmind-cli login` |
+| "Not authenticated" | Run `packmind login` |
 | "Network error" | Check connection, retry |
 | "Name must be at least 3 characters" | Use a longer name |
 

.claude/skills/packmind-create-skill/README.md

@@ -23,14 +23,14 @@ The AI agent will:
 2. Initialize the skill structure using the bundled scripts
 3. Guide you through editing the SKILL.md content
 4. Validate the skill before distribution
-5. Help you distribute it via packmind-cli
+5. Help you distribute it via packmind
 
 ## Prerequisites
 
 Before using this skill, ensure you have:
 
 - **Python 3**: Required for skill initialization and validation
-- **packmind-cli**: Required for skill distribution
+- **packmind**: Required for skill distribution
 
 ## Directory Structure
 

.claude/skills/packmind-create-skill/SKILL.md

@@ -103,16 +103,16 @@ If not available, install it:
 
 ### Packmind CLI
 
-Check if packmind-cli is installed:
+Check if packmind is installed:
 
 ```bash
-packmind-cli --version
+packmind --version
 ```
 
 If not available, install it:
 
 ```bash
-npm install -g packmind-cli
+npm install -g packmind
 ```
 
 ## Skill Creation Process
@@ -166,7 +166,7 @@ At this point, it is time to actually create the skill.
 
 Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
 
-**Before running the script**, verify that python3 and packmind-cli are available (see Prerequisites section). If not installed, install them first.
+**Before running the script**, verify that python3 and packmind are available (see Prerequisites section). If not installed, install them first.
 
 When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
 
@@ -249,12 +249,12 @@ After testing the skill, users may request improvements. Often this happens righ
 
 **After successful validation, always run the distribution command** to register the skill with Packmind. Do not skip this step.
 
-**Before running the command**, verify that packmind-cli is available (see Prerequisites section). If not installed, install it first.
+**Before running the command**, verify that packmind is available (see Prerequisites section). If not installed, install it first.
 
 Run the following command with the actual skill path:
 
 ```bash
-packmind-cli skills add <path/to/skill-folder>
+packmind skills add <path/to/skill-folder>
 ```
 
 This registers the skill with Packmind, making it available for deployment to target repositories and AI coding agents.
@@ -263,7 +263,7 @@ This registers the skill with Packmind, making it available for deployment to ta
 
 After successful distribution, check if the skill fits an existing package:
 
-1. Run `packmind-cli install --list` to get available packages
+1. Run `packmind install --list` to get available packages
 2. If no packages exist, skip this step silently and end the workflow
 3. Analyze the created skill's name and description against each package's name and description
 4. If a package is a clear semantic fit (the skill's domain/technology aligns with the package's purpose):
@@ -274,6 +274,6 @@ After successful distribution, check if the skill fits an existing package:
      - Skip
 5. If no clear fit is found, skip silently (do not mention packages)
 6. If user chooses to add:
-   - Run: `packmind-cli packages add --to <package-slug> --skill <skill-slug>`
-   - Ask: "Would you like me to run `packmind-cli install` to sync the changes?"
-   - If yes, run: `packmind-cli install`
+   - Run: `packmind packages add --to <package-slug> --skill <skill-slug>`
+   - Ask: "Would you like me to run `packmind install` to sync the changes?"
+   - If yes, run: `packmind install`

.claude/skills/packmind-create-standard/README.md

@@ -29,8 +29,8 @@ The AI agent will:
 
 Before using this skill, ensure you have:
 
-- **packmind-cli**: Required for standard creation
-- **Packmind account**: Login via `packmind-cli login`
+- **packmind**: Required for standard creation
+- **Packmind account**: Login via `packmind login`
 
 ## License
 

.claude/skills/packmind-create-standard/SKILL.md

@@ -88,12 +88,12 @@ The `# Title` heading is the **display name** shown in indexes and dashboards. T
 
 ## Prerequisites
 
-Before creating a standard, verify that packmind-cli is available:
+Before creating a standard, verify that packmind is available:
 
-Check if packmind-cli is installed:
+Check if packmind is installed:
 
 ```bash
-packmind-cli --version
+packmind --version
 ```
 
 If not available, install it:
@@ -105,7 +105,7 @@ npm install -g @packmind/cli
 Then login to Packmind:
 
 ```bash
-packmind-cli login
+packmind login
 ```
 
 ## Standard Creation Process
@@ -328,21 +328,21 @@ Rules:
 6. Pipe the JSON directly to the CLI via stdin using a heredoc (no intermediate file needed):
 
 ```bash
-packmind-cli standards create --origin-skill packmind-create-standard <<'EOF'
+packmind standards create --origin-skill packmind-create-standard <<'EOF'
 {"name":"...","description":"...","scope":"...","rules":[...]}
 EOF
 ```
 
 Expected output on success:
 ```
-packmind-cli Standard "Your Standard Name" created successfully (ID: <uuid>)
+packmind Standard "Your Standard Name" created successfully (ID: <uuid>)
 ```
 
 #### Troubleshooting
 
 **"Not logged in" error:**
 ```bash
-packmind-cli login
+packmind login
 ```
 
 **"Failed to resolve global space" error:**
@@ -368,7 +368,7 @@ After the standard is **successfully created**, delete the draft markdown file i
 
 After successful creation, check if the standard fits an existing package:
 
-1. Run `packmind-cli install --list` to get available packages
+1. Run `packmind install --list` to get available packages
 2. If no packages exist, skip this step silently and end the workflow
 3. Analyze the created standard's name, description, and scope against each package's name and description
 4. If a package is a clear semantic fit (the standard's domain/technology aligns with the package's purpose):
@@ -379,9 +379,9 @@ After successful creation, check if the standard fits an existing package:
      - Skip
 5. If no clear fit is found, skip silently (do not mention packages)
 6. If user chooses to add:
-   - Run: `packmind-cli packages add --to <package-slug> --standard <standard-slug>`
-   - Ask: "Would you like me to run `packmind-cli install` to sync the changes?"
-   - If yes, run: `packmind-cli install`
+   - Run: `packmind packages add --to <package-slug> --standard <standard-slug>`
+   - Ask: "Would you like me to run `packmind install` to sync the changes?"
+   - If yes, run: `packmind install`
 
 ## Complete Example
 
@@ -451,7 +451,7 @@ it('validates user', () => { expect(result.name).toBe('test'); expect(result.age
 
 **Creating the standard (piped via stdin):**
 ```bash
-packmind-cli standards create --origin-skill packmind-create-standard <<'EOF'
+packmind standards create --origin-skill packmind-create-standard <<'EOF'
 {"name":"TypeScript Testing Conventions","description":"Enforce consistent testing patterns...","scope":"**/*.spec.ts,**/*.test.ts","rules":[...]}
 EOF
 ```