pipecraft 0.0.0-releaseit → 0.25.0

package/README.md

@@ -1,11 +1,11 @@
-<img src="./assets/logo_banner.png" alt="PipeCraft Logo" width="auto">
+<img src="https://raw.githubusercontent.com/jamesvillarrubia/pipecraft/main/assets/logo_banner.png" alt="PipeCraft Logo" width="auto">
 
 # PipeCraft
 
-[![npm version](https://badge.fury.io/js/pipecraft.svg)](https://badge.fury.io/js/pipecraft)
+[![npm version](https://badge.fury.io/js/pipecraft.svg)](https://www.npmjs.com/package/pipecraft)
 [![License](https://img.shields.io/npm/l/pipecraft.svg)](https://github.com/jamesvillarrubia/pipecraft/blob/main/LICENSE)
 [![NPM downloads](https://img.shields.io/npm/dm/pipecraft.svg)](https://www.npmjs.com/package/pipecraft)
-[![Node.js Version](https://img.shields.io/node/v/pipecraft.svg)](https://nodejs.org/en/)
+[![Node.js Version](https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen)](https://nodejs.org/en/)
 [![codecov](https://codecov.io/gh/jamesvillarrubia/pipecraft/branch/main/graph/badge.svg)](https://codecov.io/gh/jamesvillarrubia/pipecraft)
 
 **Pipeline Status:**
@@ -30,6 +30,7 @@ PipeCraft is a powerful CLI tool for automating trunk-based development workflow
 - [Domain-Based Workflows](#domain-based-workflows)
 - [Version Management](#version-management)
 - [Examples](#examples)
+- [Documentation](#documentation)
 - [Roadmap & Future Features](#roadmap--future-features)
 - [Troubleshooting](#troubleshooting)
 - [Contributing](#contributing)
@@ -45,21 +46,23 @@ PipeCraft is a powerful CLI tool for automating trunk-based development workflow
 - **Branch Flow Management** - Support for custom branch flows (develop → staging → main)
 - **Fast-Forward Merging** - Automatic branch management with configurable merge strategies
 - **Idempotent Regeneration** - Only regenerate when configuration or templates change
-- **GitLab Support** - Works with both GitHub Actions and GitLab CI (configurable)
+- **User Job Preservation** - Regenerates pipelines while preserving your custom jobs and comments
 - **Customizable Actions** - Define actions per branch merge (tests, deploys, version bumps)
 - **GitHub Setup Automation** - Automated token and repository setup validation
 
+> **Note**: This release focuses on GitHub Actions workflows. GitLab CI/CD support is [planned](#roadmap--future-features) for a future release. Currently, the `ciProvider` field accepts `'gitlab'` but generates GitHub Actions syntax.
+
 ## Prerequisites
 
-- Git
-- A GitHub or GitLab account
-- Node.js 18+ (for npm installation)
+- **Git** - Version control system
+- **GitHub Account** - For GitHub Actions workflows
+- **Node.js 18.0.0 or higher** - For npm installation
 
 ## Quick Start
 
 1. Initialize PipeCraft in your project:
    ```bash
-   npx pipecraft init --interactive
+   npx pipecraft init
    ```
 
 2. Generate your CI/CD workflows:
@@ -118,20 +121,17 @@ PipeCraft provides several commands to manage your trunk-based development workf
 
 #### 1. Initialize Configuration
 
-Start with an interactive setup wizard:
+Create a basic configuration with default settings:
 ```bash
-pipecraft init --interactive
+pipecraft init
 ```
 
-Or create a basic configuration:
+Force overwrite existing configuration:
 ```bash
-pipecraft init --ci-provider github --initial-branch develop --final-branch main
+pipecraft init --force
 ```
 
-Include version management setup:
-```bash
-pipecraft init --with-versioning
-```
+> **Note**: The `init` command currently generates a default configuration file with standard trunk flow settings (develop → staging → main). You can then edit the `.pipecraftrc.json` file to customize branch names, domains, and other settings.
 
 #### 2. Generate Workflows
 
@@ -157,6 +157,28 @@ If any check fails, you'll see helpful error messages with suggestions. Example
    💡 Initialize git: 'git init' or clone an existing repository
 ```
 
+**Output verbosity levels:**
+
+Normal mode (default) - Clean, actionable output:
+```bash
+pipecraft generate
+```
+Shows only essential information: pre-flight checks and completion status.
+
+Verbose mode - Shows file operations:
+```bash
+pipecraft generate --verbose
+```
+Includes file merge status, config paths, and workflow generation details.
+
+Debug mode - Full internal details:
+```bash
+pipecraft generate --debug
+```
+Includes everything from verbose mode plus internal debugging information like branch flow context, job ordering, and template operations.
+
+**Other options:**
+
 Skip pre-flight checks (not recommended):
 ```bash
 pipecraft generate --skip-checks
@@ -254,10 +276,6 @@ Example `.pipecraftrc.json`:
       "breaking": "major"
     }
   },
-  "actions": {
-    "onDevelopMerge": ["runTests", "fastForwardToStaging"],
-    "onStagingMerge": ["runTests", "calculateVersion", "createOrFastForwardToMain"]
-  },
   "domains": {
     "api": {
       "paths": ["apps/api/**"],
@@ -275,17 +293,18 @@ Example `.pipecraftrc.json`:
 
 PipeCraft provides the following commands:
 
-| Command | Description | Options |
-|---------|-------------|---------|
-| `init` | Initialize PipeCraft configuration | `--interactive`, `--force`, `--with-versioning`, `--ci-provider`, `--merge-strategy`, `--initial-branch`, `--final-branch` |
-| `generate` | Generate CI/CD workflows with pre-flight checks | `--skip-checks`, `--force`, `--dry-run`, `--config`, `--output-pipeline`, `--verbose` |
+| Command | Description | Key Options |
+|---------|-------------|-------------|
+| `init` | Initialize PipeCraft configuration | `--force` |
+| `generate` | Generate CI/CD workflows with pre-flight checks | `--skip-checks`, `--force`, `--dry-run`, `--config`, `--output-pipeline`, `--verbose`, `--debug` |
 | `validate` | Validate configuration file | `--config` |
-| `validate:pipeline` | Validate generated pipeline files | `--strict` |
 | `setup-github` | Configure GitHub Actions workflow permissions | `--apply`, `--force` |
 | `verify` | Verify PipeCraft setup | None |
 | `version` | Version management commands | `--check`, `--bump`, `--release` |
 | `setup` | Create branches from branch flow | `--force` |
 
+> **Note**: All commands support global options like `--verbose` and `--debug` for detailed output.
+
 ### Global Options
 
 Available for all commands:
@@ -293,21 +312,25 @@ Available for all commands:
 - `-c, --config <path>` - Path to config file (default: `.pipecraftrc.json`)
 - `-p, --pipeline <path>` - Path to existing pipeline file for merging
 - `-o, --output-pipeline <path>` - Path to output pipeline file
-- `-v, --verbose` - Verbose output
+- `-v, --verbose` - Verbose output (shows file operations and merge status)
+- `--debug` - Debug output (includes verbose output plus internal debugging details)
 - `--force` - Force operation even if unchanged
 - `--dry-run` - Show what would be done without making changes
 
 ### Command Examples
 
 ```bash
-# Initialize with all options
-pipecraft init --interactive --with-versioning --ci-provider github
+# Initialize configuration (creates .pipecraftrc.json with defaults)
+pipecraft init
 
 # Generate workflows with custom paths
 pipecraft generate --config .pipecraft.json --output-pipeline workflows/ci.yml
 
-# Validate pipeline files
-pipecraft validate:pipeline
+# Generate with verbose output to see file operations
+pipecraft generate --verbose
+
+# Generate with debug output to see internal details
+pipecraft generate --debug
 
 # Setup GitHub Actions permissions (interactive mode)
 pipecraft setup-github
@@ -315,12 +338,16 @@ pipecraft setup-github
 # Setup GitHub Actions permissions (auto-apply mode)
 pipecraft setup-github --apply
 
-# Validate before committing
+# Validate configuration before committing
 pipecraft validate && git commit -am "chore: update workflow config"
 
-# Check version and create release
+# Check what version would be bumped to
 pipecraft version --check
+
+# Bump version based on conventional commits
 pipecraft version --bump
+
+# Create a full release with tag and changelog
 pipecraft version --release
 
 # Setup all branches for new repository
@@ -589,33 +616,6 @@ Note: Branch protection rules are required for auto-merge to work in GitHub.
 | `semver.bumpRules.fix` | `'major' \| 'minor' \| 'patch'` | Version bump for fixes |
 | `semver.bumpRules.breaking` | `'major' \| 'minor' \| 'patch'` | Version bump for breaking changes |
 
-### Actions
-
-Define what happens on branch merges:
-
-```json
-{
-  "actions": {
-    "onDevelopMerge": [
-      "runTests",
-      "fastForwardToStaging"
-    ],
-    "onStagingMerge": [
-      "runTests",
-      "calculateVersion",
-      "createOrFastForwardToMain"
-    ]
-  }
-}
-```
-
-Available actions:
-- `runTests` - Run test suite
-- `fastForwardToStaging` - Fast-forward develop to staging
-- `calculateVersion` - Calculate next semantic version
-- `createOrFastForwardToMain` - Merge or fast-forward to main
-- `deploy` - Run deployment steps
-
 ### Domains (Monorepo Support)
 
 Define multiple domains for path-based change detection:
@@ -836,12 +836,6 @@ Configuration for staging environment:
       "breaking": "major"
     }
   },
-  "actions": {
-    "onDevelopMerge": ["runTests", "fastForwardToStaging"],
-    "onStagingMerge": ["runTests", "deployToStaging"],
-    "onUatMerge": ["runTests", "calculateVersion", "deployToUat"],
-    "onProductionMerge": ["runTests", "deployToProduction", "createRelease"]
-  },
   "domains": {
     "api": {
       "paths": ["services/api/**", "libs/api-core/**"],
@@ -913,49 +907,71 @@ Configuration with non-standard branch names:
 }
 ```
 
+## Documentation
+
+PipeCraft provides comprehensive documentation for different aspects of the project:
+
+### Core Documentation
+
+- **[ARCHITECTURE.md](./docs/ARCHITECTURE.md)** - System architecture overview, design patterns, and component interactions
+- **[CURRENT_TRUNK_FLOW.md](./docs/CURRENT_TRUNK_FLOW.md)** - Current implemented trunk-based development workflow
+- **[ERROR_HANDLING.md](./docs/ERROR_HANDLING.md)** - Error handling strategies and common error scenarios
+- **[TESTING_GUIDE.md](./TESTING_GUIDE.md)** - Complete testing guide with examples and best practices
+
+### Development Documentation
+
+- **[tests/README.md](./tests/README.md)** - Test structure and organization
+- **[docs/REPO_CLEANUP_PLAN.md](./docs/REPO_CLEANUP_PLAN.md)** - Repository organization and structure
+
+### Planning Documents
+
+- **[TRUNK_FLOW_PLAN.md](./TRUNK_FLOW_PLAN.md)** - Future roadmap for trunk flow variations *(future plans, not current implementation)*
+
+### Quick Links
+
+- **Architecture**: Understand how PipeCraft works internally
+- **Current Trunk Flow**: See what's implemented in this release
+- **Testing Guide**: Learn how to test PipeCraft or contribute tests
+- **Error Handling**: Debug issues and understand error messages
+
 ## Roadmap & Future Features
 
-PipeCraft is actively being developed with plans for additional features and improvements:
+PipeCraft is actively being developed with plans for additional features and improvements.
+
+### Current Release (v1.x)
+
+This release focuses on a **solid, working trunk-based development workflow** for GitHub Actions with:
+
+✅ **Develop → Staging → Main** branch flow  
+✅ **Domain-based change detection** for monorepos  
+✅ **Semantic versioning** with conventional commits  
+✅ **User job preservation** during regeneration  
+✅ **Pre-flight checks** for smooth setup  
+✅ **Comprehensive documentation** and testing  
+
+See [CURRENT_TRUNK_FLOW.md](./docs/CURRENT_TRUNK_FLOW.md) for details on what's implemented.
 
 ### Planned Features
 
-#### Enhanced GitLab Support
-- Full GitLab CI/CD pipeline generation (currently basic support)
-- GitLab-specific features (includes, extends, etc.)
-- GitLab merge request automation
-- GitLab runner configuration
-
-#### Additional Workflow Patterns
-- Feature branch workflows (Gitflow alternative)
-- Release branch workflows
-- Hotfix workflows
-- Custom workflow patterns via plugins
-
-#### Advanced Branch Management
-- Automatic conflict resolution strategies
-- Branch protection rule setup
-- PR template generation
-- Code review automation
-
-#### Extended CI/CD Providers
-- Azure DevOps Pipelines
-- Jenkins pipeline generation
-- CircleCI configuration
-- Bitbucket Pipelines
-
-#### Improved Developer Experience
-- Interactive CLI improvements
-- Better error messages and diagnostics
-- Configuration migration tools
-- Visual workflow editor (web-based)
-- Real-time workflow preview
-
-#### Enterprise Features
-- Team configuration templates
-- Organization-wide policy enforcement
-- Audit logging
-- RBAC integration
-- Self-hosted runner configuration
+The roadmap is documented in [TRUNK_FLOW_PLAN.md](./TRUNK_FLOW_PLAN.md). Key planned features include:
+
+#### Short Term (v2.x)
+- **Enhanced GitLab Support** - Full GitLab CI/CD pipeline generation
+- **Interactive Configuration** - Interactive `init` command with prompts
+- **Additional Flow Variations** - Gitflow, release branches, hotfix workflows
+- **CLI Improvements** - Better error messages, configuration migration tools
+
+#### Medium Term (v3.x)
+- **Extended CI/CD Providers** - Azure DevOps, Jenkins, CircleCI, Bitbucket
+- **Advanced Branch Management** - Conflict resolution, PR templates
+- **Visual Workflow Editor** - Web-based workflow configuration tool
+
+#### Long Term (v4.x+)
+- **Enterprise Features** - Team templates, policy enforcement, audit logging
+- **Plugin System** - Custom workflow patterns and extensions
+- **Multi-Repository** Support - Manage pipelines across multiple repos
+
+For the complete roadmap and feature comparison, see [TRUNK_FLOW_PLAN.md](./TRUNK_FLOW_PLAN.md).
 
 ### Contributing to the Roadmap
 
@@ -980,6 +996,7 @@ Have a feature request? We'd love to hear from you!
 - Check if configuration is valid: `pipecraft validate`
 - Use `--force` to bypass cache: `pipecraft generate --force`
 - Use `--verbose` for detailed output: `pipecraft generate --verbose`
+- Use `--debug` for full debugging output: `pipecraft generate --debug`
 - Verify file permissions in `.github/workflows/`
 
 #### 2. Configuration Validation Errors
@@ -1028,16 +1045,17 @@ If you encounter issues not covered here:
 
 1. Check the [GitHub Issues](https://github.com/jamesvillarrubia/pipecraft/issues)
 2. Enable verbose logging: `pipecraft generate --verbose`
-3. Validate your configuration: `pipecraft validate`
-4. [Open a new issue](https://github.com/jamesvillarrubia/pipecraft/issues/new) with:
+3. Enable debug logging for more detail: `pipecraft generate --debug`
+4. Validate your configuration: `pipecraft validate`
+5. [Open a new issue](https://github.com/jamesvillarrubia/pipecraft/issues/new) with:
    - PipeCraft version: `pipecraft --version`
    - Node version: `node --version`
    - Your configuration (sanitized)
-   - Full error output with `--verbose`
+   - Full error output with `--debug`
 
 ## Contributing
 
-Contributions are welcome! Please see [CONTRIBUTING.md](./CONTRIBUTING.md) for details on:
+Contributions are welcome! Please see [CONTRIBUTING.md](https://github.com/jamesvillarrubia/pipecraft/blob/main/CONTRIBUTING.md) for details on:
 
 - Code of conduct
 - Development setup
@@ -1080,7 +1098,7 @@ npm test tests/unit/config.test.ts
 
 ## License
 
-This project is licensed under the MIT License - see the [LICENSE](./LICENSE) file for details.
+This project is licensed under the MIT License - see the [LICENSE](https://github.com/jamesvillarrubia/pipecraft/blob/main/LICENSE) file for details.
 
 ## Acknowledgments
 

package/dist/cli/index.d.ts

@@ -1,3 +1,72 @@
 #!/usr/bin/env node
+/**
+ * PipeCraft Command-Line Interface
+ *
+ * Main CLI entry point for PipeCraft - automated CI/CD pipeline generator for
+ * trunk-based development workflows. This CLI provides commands for:
+ *
+ * - **init**: Initialize PipeCraft configuration interactively or with flags
+ * - **generate**: Generate GitHub Actions workflows from configuration
+ * - **validate**: Validate existing workflows and configuration
+ * - **verify**: Verify pipeline structure and job order
+ * - **setup**: Configure GitHub repository permissions and settings
+ * - **version**: Display version information
+ *
+ * ## Command Overview
+ *
+ * ### init
+ * Creates .pipecraftrc.json configuration file with project settings.
+ * Can run interactively or accept flags for automation.
+ *
+ * ### generate
+ * Generates GitHub Actions workflows based on configuration:
+ * - Main pipeline workflow (.github/workflows/pipeline.yml)
+ * - Reusable actions (.github/actions/*)
+ * - Idempotent regeneration (only when config/templates change)
+ *
+ * ### validate
+ * Validates workflow YAML syntax and structure, checks for common issues.
+ *
+ * ### verify
+ * Verifies pipeline job order and dependencies are correct.
+ *
+ * ### setup
+ * Configures GitHub repository:
+ * - Workflow permissions (read/write)
+ * - Branch protection rules
+ * - Auto-merge settings
+ *
+ * ## Global Options
+ * - `-c, --config <path>`: Path to config file (default: .pipecraftrc.json)
+ * - `-v, --verbose`: Verbose output
+ * - `--debug`: Debug output (maximum detail)
+ * - `--force`: Force regeneration even if unchanged
+ * - `--dry-run`: Show what would be done without making changes
+ *
+ * ## Examples
+ *
+ * ```bash
+ * # Initialize configuration interactively
+ * pipecraft init --interactive
+ *
+ * # Generate workflows
+ * pipecraft generate
+ *
+ * # Generate with version management
+ * pipecraft init --with-versioning
+ * pipecraft generate
+ *
+ * # Validate existing workflows
+ * pipecraft validate
+ *
+ * # Setup GitHub repository
+ * pipecraft setup --verify
+ *
+ * # Debug mode
+ * pipecraft generate --debug
+ * ```
+ *
+ * @module cli
+ */
 export {};
 //# sourceMappingURL=index.d.ts.map

package/dist/cli/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":""}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoEG"}

package/dist/cli/index.js

@@ -1,6 +1,73 @@
 #!/usr/bin/env node
-// PipeCraft CLI - Automated CI/CD pipeline generator
-// Test change for deploy flow validation
+/**
+ * PipeCraft Command-Line Interface
+ *
+ * Main CLI entry point for PipeCraft - automated CI/CD pipeline generator for
+ * trunk-based development workflows. This CLI provides commands for:
+ *
+ * - **init**: Initialize PipeCraft configuration interactively or with flags
+ * - **generate**: Generate GitHub Actions workflows from configuration
+ * - **validate**: Validate existing workflows and configuration
+ * - **verify**: Verify pipeline structure and job order
+ * - **setup**: Configure GitHub repository permissions and settings
+ * - **version**: Display version information
+ *
+ * ## Command Overview
+ *
+ * ### init
+ * Creates .pipecraftrc.json configuration file with project settings.
+ * Can run interactively or accept flags for automation.
+ *
+ * ### generate
+ * Generates GitHub Actions workflows based on configuration:
+ * - Main pipeline workflow (.github/workflows/pipeline.yml)
+ * - Reusable actions (.github/actions/*)
+ * - Idempotent regeneration (only when config/templates change)
+ *
+ * ### validate
+ * Validates workflow YAML syntax and structure, checks for common issues.
+ *
+ * ### verify
+ * Verifies pipeline job order and dependencies are correct.
+ *
+ * ### setup
+ * Configures GitHub repository:
+ * - Workflow permissions (read/write)
+ * - Branch protection rules
+ * - Auto-merge settings
+ *
+ * ## Global Options
+ * - `-c, --config <path>`: Path to config file (default: .pipecraftrc.json)
+ * - `-v, --verbose`: Verbose output
+ * - `--debug`: Debug output (maximum detail)
+ * - `--force`: Force regeneration even if unchanged
+ * - `--dry-run`: Show what would be done without making changes
+ *
+ * ## Examples
+ *
+ * ```bash
+ * # Initialize configuration interactively
+ * pipecraft init --interactive
+ *
+ * # Generate workflows
+ * pipecraft generate
+ *
+ * # Generate with version management
+ * pipecraft init --with-versioning
+ * pipecraft generate
+ *
+ * # Validate existing workflows
+ * pipecraft validate
+ *
+ * # Setup GitHub repository
+ * pipecraft setup --verify
+ *
+ * # Debug mode
+ * pipecraft generate --debug
+ * ```
+ *
+ * @module cli
+ */
 import { Command } from 'commander';
 import { cosmiconfigSync } from 'cosmiconfig';
 import { runModule, prompt } from '@featherscloud/pinion';
@@ -12,6 +79,7 @@ import { VersionManager } from '../utils/versioning.js';
 import { loadConfig, validateConfig } from '../utils/config.js';
 import { setupGitHubPermissions } from '../utils/github-setup.js';
 import { runPreflightChecks, formatPreflightResults } from '../utils/preflight.js';
+import { logger } from '../utils/logger.js';
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 const program = new Command();
@@ -27,6 +95,7 @@ program
     .option('-p, --pipeline <path>', 'path to existing pipeline file for merging', '.github/workflows/pipeline.yml')
     .option('-o, --output-pipeline <path>', 'path to output pipeline file (for testing)', '.github/workflows/pipeline.yml')
     .option('-v, --verbose', 'verbose output')
+    .option('--debug', 'debug output (includes all verbose output plus additional debugging info)')
     .option('--force', 'force regeneration even if files unchanged')
     .option('--dry-run', 'show what would be done without making changes');
 // Init command - Initialize configuration
@@ -91,44 +160,47 @@ program
         const configPath = globalOptions.config;
         const pipelinePath = globalOptions.pipeline;
         const outputPipelinePath = globalOptions.outputPipeline;
+        // Set logger level based on flags
+        if (globalOptions.debug) {
+            logger.setLevel('debug');
+        }
+        else if (globalOptions.verbose) {
+            logger.setLevel('verbose');
+        }
         // Run pre-flight checks unless skipped
         if (!options.skipChecks) {
-            console.log('🔍 Running pre-flight checks...\n');
+            logger.info('🔍 Running pre-flight checks...\n');
             const checks = runPreflightChecks();
             const { allPassed, output, nextSteps } = formatPreflightResults(checks);
-            console.log(output);
-            console.log();
+            logger.info(output);
+            logger.info('');
             if (!allPassed) {
-                console.error('❌ Pre-flight checks failed. Fix the issues above and try again.');
-                console.error('   Or use --skip-checks to bypass (not recommended)\n');
+                logger.error('❌ Pre-flight checks failed. Fix the issues above and try again.');
+                logger.error('   Or use --skip-checks to bypass (not recommended)\n');
                 process.exit(1);
             }
-            console.log('✅ All pre-flight checks passed!');
+            logger.info('✅ All pre-flight checks passed!');
             // Store next steps for later display (after successful generation)
             if (nextSteps) {
                 options._nextSteps = nextSteps;
             }
-            console.log();
-        }
-        if (globalOptions.verbose) {
-            console.log(`📖 Reading config from: ${configPath}`);
-            console.log(`📖 Reading pipeline from: ${pipelinePath}`);
+            logger.info('');
         }
+        logger.verbose(`📖 Reading config from: ${configPath}`);
+        logger.verbose(`📖 Reading pipeline from: ${pipelinePath}`);
         // Load configuration
         const config = loadConfig(configPath);
         // Check idempotency if not forcing
         if (!globalOptions.force && !globalOptions.dryRun) {
             const idempotencyManager = new IdempotencyManager(config);
             if (!(await idempotencyManager.hasChanges())) {
-                console.log('ℹ️  No changes detected. Use --force to regenerate anyway.');
+                logger.info('ℹ️  No changes detected. Use --force to regenerate anyway.');
                 return;
             }
-            if (globalOptions.verbose) {
-                console.log('🔄 Changes detected, regenerating workflows...');
-            }
+            logger.verbose('🔄 Changes detected, regenerating workflows...');
         }
         if (globalOptions.dryRun) {
-            console.log('🔍 Dry run mode - would generate workflows');
+            logger.info('🔍 Dry run mode - would generate workflows');
             return;
         }
         await runModule(join(__dirname, '../generators/workflows.tpl.js'), {
@@ -158,16 +230,16 @@ program
         // Update idempotency cache
         const idempotencyManager = new IdempotencyManager(config);
         await idempotencyManager.updateCache();
-        console.log(`✅ Generated workflows in: ${options.output}`);
+        logger.success(`✅ Generated workflows in: ${options.output}`);
         // Display next steps if available
         if (options._nextSteps) {
-            console.log();
+            logger.info('');
             const steps = options._nextSteps;
-            steps.forEach((step) => console.log(step));
+            steps.forEach((step) => logger.info(step));
         }
     }
     catch (error) {
-        console.error('❌ Failed to generate workflows:', error.message);
+        logger.error('❌ Failed to generate workflows:', error.message);
         process.exit(1);
     }
 });