mcli-framework 7.10.2__tar.gz → 7.11.1__tar.gz

{mcli_framework-7.10.2 → mcli_framework-7.11.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcli-framework
-Version: 7.10.2
+Version: 7.11.1
 Summary: Portable workflow framework - transform any script into a versioned, schedulable command. Store in ~/.mcli/commands/, version with lockfile, run as daemon or cron job.
 Author-email: Luis Fernandez de la Vara <luis@lefv.io>
 Maintainer-email: Luis Fernandez de la Vara <luis@lefv.io>
@@ -216,6 +216,24 @@ pip install mcli-framework
 uv pip install mcli-framework
 ```
 
+### Initialize Workflows Directory
+
+```bash
+# Initialize workflows in current git repository
+mcli workflow init
+
+# Or initialize global workflows
+mcli workflow init --global
+
+# Initialize with git repository for workflows
+mcli workflow init --git
+```
+
+This creates a `.mcli/workflows/` directory (local to your repo) or `~/.mcli/workflows/` (global) with:
+- README.md with usage instructions
+- commands.lock.json for version tracking
+- .gitignore for backup files
+
 ### Create Your First Workflow
 
 #### Method 1: From a Python Script
@@ -233,20 +251,20 @@ def app(message):
 EOF
 
 # Import as workflow
-mcli commands import-script my_task.py --name my-task --group workflow
+mcli workflow import-script my_task.py --name my-task
 
 # Run it
-mcli workflow my-task --message "Hi"
+mcli workflowss my-task --message "Hi"
 ```
 
 #### Method 2: Interactive Creation
 
 ```bash
 # Create workflow interactively
-mcli commands add my-task --group workflow
+mcli workflow add my-task
 
 # Edit in your $EDITOR, then run
-mcli workflow my-task
+mcli workflowss my-task
 ```
 
 ## 📦 Workflow System Features
@@ -257,29 +275,28 @@ Multiple ways to create workflows:
 
 ```bash
 # Import from existing Python script
-mcli commands import-script script.py --name my-workflow --group workflow
-
+mcli workflow import-script script.py --name my-workflow
 # Create new workflow interactively
-mcli commands add my-workflow --group workflow --description "Does something useful"
+mcli workflow add my-workflow --group workflow --description "Does something useful"
 
 # List all workflows
-mcli commands list-custom
+mcli workflow list-custom
 ```
 
 ### 2. **Edit & Manage Workflows**
 
 ```bash
 # Edit workflow in $EDITOR
-mcli commands edit my-workflow
+mcli workflow edit my-workflow
 
 # Show workflow details
-mcli commands info my-workflow
+mcli workflow info my-workflow
 
 # Search workflows
-mcli commands search "pdf"
+mcli workflow search "pdf"
 
 # Remove workflow
-mcli commands remove my-workflow
+mcli workflow remove my-workflow
 ```
 
 ### 3. **Export & Import (Portability)**
@@ -288,13 +305,13 @@ Share workflows across machines or with your team:
 
 ```bash
 # Export all workflows to JSON
-mcli commands export my-workflows.json
+mcli workflow export my-workflows.json
 
 # Import on another machine
-mcli commands import my-workflows.json
+mcli workflow import my-workflows.json
 
 # Export single workflow to Python script
-mcli commands export-script my-workflow --output my_workflow.py
+mcli workflow export-script my-workflow --output my_workflow.py
 ```
 
 Your workflows are just JSON files in `~/.mcli/commands/`:
@@ -313,10 +330,10 @@ MCLI automatically maintains a lockfile for reproducibility:
 
 ```bash
 # Update lockfile with current workflow versions
-mcli commands update-lockfile
+mcli workflow update-lockfile
 
 # Verify workflows match lockfile
-mcli commands verify
+mcli workflow verify
 ```
 
 Example `commands.lock.json`:
@@ -346,7 +363,7 @@ git commit -m "Update workflows"
 
 # On another machine
 git pull
-mcli commands verify  # Ensures consistency
+mcli workflow verify  # Ensures consistency
 ```
 
 ### 5. **Run as Daemon or Scheduled Task**
@@ -357,29 +374,29 @@ Workflows aren't coupled to the engine - run them however you want:
 
 ```bash
 # Start workflow as background daemon
-mcli workflow daemon start my-task-daemon --workflow my-task
+mcli workflows daemon start my-task-daemon --workflow my-task
 
 # Check daemon status
-mcli workflow daemon status
+mcli workflows daemon status
 
 # Stop daemon
-mcli workflow daemon stop my-task-daemon
+mcli workflows daemon stop my-task-daemon
 ```
 
 #### As Scheduled Task:
 
 ```bash
 # Schedule workflow to run every hour
-mcli workflow scheduler add \
+mcli workflows scheduler add \
   --name hourly-sync \
   --schedule "0 * * * *" \
   --workflow my-task
 
 # List scheduled workflows
-mcli workflow scheduler list
+mcli workflows scheduler list
 
 # View logs
-mcli workflow scheduler logs hourly-sync
+mcli workflows scheduler logs hourly-sync
 ```
 
 ## 🎨 Real-World Workflow Examples
@@ -388,12 +405,11 @@ mcli workflow scheduler logs hourly-sync
 
 ```bash
 # Create PDF processing workflow
-mcli commands import-script pdf_tool.py --name pdf --group workflow
-
+mcli workflow import-script pdf_tool.py --name pdf
 # Use it
-mcli workflow pdf extract ~/Documents/report.pdf
-mcli workflow pdf compress ~/Documents/*.pdf --output compressed/
-mcli workflow pdf split large.pdf --pages 10
+mcli workflows pdf extract ~/Documents/report.pdf
+mcli workflows pdf compress ~/Documents/*.pdf --output compressed/
+mcli workflows pdf split large.pdf --pages 10
 ```
 
 ### Example 2: Data Sync Workflow
@@ -423,13 +439,12 @@ def status():
     click.echo("Checking sync status...")
 EOF
 
-mcli commands import-script sync.py --name sync --group workflow
-
+mcli workflow import-script sync.py --name sync
 # Run manually
-mcli workflow sync backup ~/data remote:backup
+mcli workflows sync backup ~/data remote:backup
 
 # Or schedule it
-mcli workflow scheduler add \
+mcli workflows scheduler add \
   --name nightly-backup \
   --schedule "0 2 * * *" \
   --workflow "sync backup ~/data remote:backup"
@@ -439,13 +454,12 @@ mcli workflow scheduler add \
 
 ```bash
 # Already included as built-in workflow
-mcli workflow git-commit
+mcli workflows git-commit
 
 # Or create your own variant
-mcli commands export-script git-commit --output my_git_helper.py
+mcli workflow export-script git-commit --output my_git_helper.py
 # Edit my_git_helper.py to customize
-mcli commands import-script my_git_helper.py --name my-git --group workflow
-```
+mcli workflow import-script my_git_helper.py --name my-git```
 
 ## 🔧 Workflow Structure
 
@@ -471,7 +485,7 @@ Each workflow is a JSON file with this structure:
 MCLI comes with powerful built-in workflows:
 
 ```bash
-mcli workflow --help
+mcli workflows --help
 ```
 
 Available workflows:
@@ -515,8 +529,8 @@ You write scripts. They work. Then:
 mcli self completion install
 
 # Now use tab completion
-mcli workflow <TAB>          # Shows all workflows
-mcli workflow pdf <TAB>      # Shows pdf subcommands
+mcli workflows <TAB>          # Shows all workflows
+mcli workflows pdf <TAB>      # Shows pdf subcommands
 ```
 
 ### AI Chat Integration
@@ -562,10 +576,13 @@ make wheel
 
 ## 📖 Documentation
 
-- **Installation**: See [Installation Guide](docs/setup/INSTALLATION.md)
+- **📚 Documentation Index**: [Complete Documentation Index](docs/INDEX.md) - All docs organized by category
+- **Installation**: See [Installation Guide](docs/setup/INSTALL.md)
 - **Workflows**: Full workflow documentation (this README)
 - **Shell Completion**: See [Shell Completion Guide](docs/features/SHELL_COMPLETION.md)
+- **Testing**: See [Testing Guide](docs/development/TESTING.md)
 - **Contributing**: See [Contributing Guide](CONTRIBUTING.md)
+- **Release Notes**: See [Latest Release (7.10.2)](docs/releases/7.10.2.md)
 
 ## 🎯 Common Use Cases
 
@@ -573,21 +590,20 @@ make wheel
 
 ```bash
 # Create your daily automation
-mcli commands add daily-tasks --group workflow
-# Add your tasks in $EDITOR
-mcli workflow scheduler add --name daily --schedule "0 9 * * *" --workflow daily-tasks
+mcli workflow add daily-tasks# Add your tasks in $EDITOR
+mcli workflows scheduler add --name daily --schedule "0 9 * * *" --workflow daily-tasks
 ```
 
 ### Use Case 2: Team Workflow Sharing
 
 ```bash
 # On your machine
-mcli commands export team-workflows.json
+mcli workflow export team-workflows.json
 
 # Share file with team
 # On teammate's machine
-mcli commands import team-workflows.json
-mcli commands verify  # Ensure consistency
+mcli workflow import team-workflows.json
+mcli workflow verify  # Ensure consistency
 ```
 
 ### Use Case 3: CI/CD Integration
@@ -595,9 +611,9 @@ mcli commands verify  # Ensure consistency
 ```bash
 # In your CI pipeline
 - pip install mcli-framework
-- mcli commands import ci-workflows.json
-- mcli workflow build-and-test
-- mcli workflow deploy --env production
+- mcli workflow import ci-workflows.json
+- mcli workflows build-and-test
+- mcli workflows deploy --env production
 ```
 
 ## 📦 Dependencies
@@ -627,7 +643,7 @@ We welcome contributions! Especially workflow examples.
 1. Fork the repository
 2. Create feature branch: `git checkout -b feature/awesome-workflow`
 3. Create your workflow
-4. Export it: `mcli commands export my-workflow.json`
+4. Export it: `mcli workflow export my-workflow.json`
 5. Submit PR with workflow JSON
 
 ## 📄 License
@@ -646,5 +662,4 @@ MIT License - see [LICENSE](LICENSE) for details.
 
 ```bash
 pip install mcli-framework
-mcli commands add my-first-workflow --group workflow
-```
+mcli workflow add my-first-workflow```

{mcli_framework-7.10.2 → mcli_framework-7.11.1}/README.md

@@ -56,6 +56,24 @@ pip install mcli-framework
 uv pip install mcli-framework
 ```
 
+### Initialize Workflows Directory
+
+```bash
+# Initialize workflows in current git repository
+mcli workflow init
+
+# Or initialize global workflows
+mcli workflow init --global
+
+# Initialize with git repository for workflows
+mcli workflow init --git
+```
+
+This creates a `.mcli/workflows/` directory (local to your repo) or `~/.mcli/workflows/` (global) with:
+- README.md with usage instructions
+- commands.lock.json for version tracking
+- .gitignore for backup files
+
 ### Create Your First Workflow
 
 #### Method 1: From a Python Script
@@ -73,20 +91,20 @@ def app(message):
 EOF
 
 # Import as workflow
-mcli commands import-script my_task.py --name my-task --group workflow
+mcli workflow import-script my_task.py --name my-task
 
 # Run it
-mcli workflow my-task --message "Hi"
+mcli workflowss my-task --message "Hi"
 ```
 
 #### Method 2: Interactive Creation
 
 ```bash
 # Create workflow interactively
-mcli commands add my-task --group workflow
+mcli workflow add my-task
 
 # Edit in your $EDITOR, then run
-mcli workflow my-task
+mcli workflowss my-task
 ```
 
 ## 📦 Workflow System Features
@@ -97,29 +115,28 @@ Multiple ways to create workflows:
 
 ```bash
 # Import from existing Python script
-mcli commands import-script script.py --name my-workflow --group workflow
-
+mcli workflow import-script script.py --name my-workflow
 # Create new workflow interactively
-mcli commands add my-workflow --group workflow --description "Does something useful"
+mcli workflow add my-workflow --group workflow --description "Does something useful"
 
 # List all workflows
-mcli commands list-custom
+mcli workflow list-custom
 ```
 
 ### 2. **Edit & Manage Workflows**
 
 ```bash
 # Edit workflow in $EDITOR
-mcli commands edit my-workflow
+mcli workflow edit my-workflow
 
 # Show workflow details
-mcli commands info my-workflow
+mcli workflow info my-workflow
 
 # Search workflows
-mcli commands search "pdf"
+mcli workflow search "pdf"
 
 # Remove workflow
-mcli commands remove my-workflow
+mcli workflow remove my-workflow
 ```
 
 ### 3. **Export & Import (Portability)**
@@ -128,13 +145,13 @@ Share workflows across machines or with your team:
 
 ```bash
 # Export all workflows to JSON
-mcli commands export my-workflows.json
+mcli workflow export my-workflows.json
 
 # Import on another machine
-mcli commands import my-workflows.json
+mcli workflow import my-workflows.json
 
 # Export single workflow to Python script
-mcli commands export-script my-workflow --output my_workflow.py
+mcli workflow export-script my-workflow --output my_workflow.py
 ```
 
 Your workflows are just JSON files in `~/.mcli/commands/`:
@@ -153,10 +170,10 @@ MCLI automatically maintains a lockfile for reproducibility:
 
 ```bash
 # Update lockfile with current workflow versions
-mcli commands update-lockfile
+mcli workflow update-lockfile
 
 # Verify workflows match lockfile
-mcli commands verify
+mcli workflow verify
 ```
 
 Example `commands.lock.json`:
@@ -186,7 +203,7 @@ git commit -m "Update workflows"
 
 # On another machine
 git pull
-mcli commands verify  # Ensures consistency
+mcli workflow verify  # Ensures consistency
 ```
 
 ### 5. **Run as Daemon or Scheduled Task**
@@ -197,29 +214,29 @@ Workflows aren't coupled to the engine - run them however you want:
 
 ```bash
 # Start workflow as background daemon
-mcli workflow daemon start my-task-daemon --workflow my-task
+mcli workflows daemon start my-task-daemon --workflow my-task
 
 # Check daemon status
-mcli workflow daemon status
+mcli workflows daemon status
 
 # Stop daemon
-mcli workflow daemon stop my-task-daemon
+mcli workflows daemon stop my-task-daemon
 ```
 
 #### As Scheduled Task:
 
 ```bash
 # Schedule workflow to run every hour
-mcli workflow scheduler add \
+mcli workflows scheduler add \
   --name hourly-sync \
   --schedule "0 * * * *" \
   --workflow my-task
 
 # List scheduled workflows
-mcli workflow scheduler list
+mcli workflows scheduler list
 
 # View logs
-mcli workflow scheduler logs hourly-sync
+mcli workflows scheduler logs hourly-sync
 ```
 
 ## 🎨 Real-World Workflow Examples
@@ -228,12 +245,11 @@ mcli workflow scheduler logs hourly-sync
 
 ```bash
 # Create PDF processing workflow
-mcli commands import-script pdf_tool.py --name pdf --group workflow
-
+mcli workflow import-script pdf_tool.py --name pdf
 # Use it
-mcli workflow pdf extract ~/Documents/report.pdf
-mcli workflow pdf compress ~/Documents/*.pdf --output compressed/
-mcli workflow pdf split large.pdf --pages 10
+mcli workflows pdf extract ~/Documents/report.pdf
+mcli workflows pdf compress ~/Documents/*.pdf --output compressed/
+mcli workflows pdf split large.pdf --pages 10
 ```
 
 ### Example 2: Data Sync Workflow
@@ -263,13 +279,12 @@ def status():
     click.echo("Checking sync status...")
 EOF
 
-mcli commands import-script sync.py --name sync --group workflow
-
+mcli workflow import-script sync.py --name sync
 # Run manually
-mcli workflow sync backup ~/data remote:backup
+mcli workflows sync backup ~/data remote:backup
 
 # Or schedule it
-mcli workflow scheduler add \
+mcli workflows scheduler add \
   --name nightly-backup \
   --schedule "0 2 * * *" \
   --workflow "sync backup ~/data remote:backup"
@@ -279,13 +294,12 @@ mcli workflow scheduler add \
 
 ```bash
 # Already included as built-in workflow
-mcli workflow git-commit
+mcli workflows git-commit
 
 # Or create your own variant
-mcli commands export-script git-commit --output my_git_helper.py
+mcli workflow export-script git-commit --output my_git_helper.py
 # Edit my_git_helper.py to customize
-mcli commands import-script my_git_helper.py --name my-git --group workflow
-```
+mcli workflow import-script my_git_helper.py --name my-git```
 
 ## 🔧 Workflow Structure
 
@@ -311,7 +325,7 @@ Each workflow is a JSON file with this structure:
 MCLI comes with powerful built-in workflows:
 
 ```bash
-mcli workflow --help
+mcli workflows --help
 ```
 
 Available workflows:
@@ -355,8 +369,8 @@ You write scripts. They work. Then:
 mcli self completion install
 
 # Now use tab completion
-mcli workflow <TAB>          # Shows all workflows
-mcli workflow pdf <TAB>      # Shows pdf subcommands
+mcli workflows <TAB>          # Shows all workflows
+mcli workflows pdf <TAB>      # Shows pdf subcommands
 ```
 
 ### AI Chat Integration
@@ -402,10 +416,13 @@ make wheel
 
 ## 📖 Documentation
 
-- **Installation**: See [Installation Guide](docs/setup/INSTALLATION.md)
+- **📚 Documentation Index**: [Complete Documentation Index](docs/INDEX.md) - All docs organized by category
+- **Installation**: See [Installation Guide](docs/setup/INSTALL.md)
 - **Workflows**: Full workflow documentation (this README)
 - **Shell Completion**: See [Shell Completion Guide](docs/features/SHELL_COMPLETION.md)
+- **Testing**: See [Testing Guide](docs/development/TESTING.md)
 - **Contributing**: See [Contributing Guide](CONTRIBUTING.md)
+- **Release Notes**: See [Latest Release (7.10.2)](docs/releases/7.10.2.md)
 
 ## 🎯 Common Use Cases
 
@@ -413,21 +430,20 @@ make wheel
 
 ```bash
 # Create your daily automation
-mcli commands add daily-tasks --group workflow
-# Add your tasks in $EDITOR
-mcli workflow scheduler add --name daily --schedule "0 9 * * *" --workflow daily-tasks
+mcli workflow add daily-tasks# Add your tasks in $EDITOR
+mcli workflows scheduler add --name daily --schedule "0 9 * * *" --workflow daily-tasks
 ```
 
 ### Use Case 2: Team Workflow Sharing
 
 ```bash
 # On your machine
-mcli commands export team-workflows.json
+mcli workflow export team-workflows.json
 
 # Share file with team
 # On teammate's machine
-mcli commands import team-workflows.json
-mcli commands verify  # Ensure consistency
+mcli workflow import team-workflows.json
+mcli workflow verify  # Ensure consistency
 ```
 
 ### Use Case 3: CI/CD Integration
@@ -435,9 +451,9 @@ mcli commands verify  # Ensure consistency
 ```bash
 # In your CI pipeline
 - pip install mcli-framework
-- mcli commands import ci-workflows.json
-- mcli workflow build-and-test
-- mcli workflow deploy --env production
+- mcli workflow import ci-workflows.json
+- mcli workflows build-and-test
+- mcli workflows deploy --env production
 ```
 
 ## 📦 Dependencies
@@ -467,7 +483,7 @@ We welcome contributions! Especially workflow examples.
 1. Fork the repository
 2. Create feature branch: `git checkout -b feature/awesome-workflow`
 3. Create your workflow
-4. Export it: `mcli commands export my-workflow.json`
+4. Export it: `mcli workflow export my-workflow.json`
 5. Submit PR with workflow JSON
 
 ## 📄 License
@@ -486,5 +502,4 @@ MIT License - see [LICENSE](LICENSE) for details.
 
 ```bash
 pip install mcli-framework
-mcli commands add my-first-workflow --group workflow
-```
+mcli workflow add my-first-workflow```

{mcli_framework-7.10.2 → mcli_framework-7.11.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mcli-framework"
-version = "7.10.2"
+version = "7.11.1"
 description = "Portable workflow framework - transform any script into a versioned, schedulable command. Store in ~/.mcli/commands/, version with lockfile, run as daemon or cron job."
 readme = "README.md"
 requires-python = ">=3.9"