agileflow 3.4.3 → 4.0.0-alpha.10

package/src/core/commands/migrate/codemods.md

@@ -1,151 +0,0 @@
----
-description: Generate and execute AST-based codemods for automated code transformations with dry-run preview and rollback support
-argument-hint: "[transformation] [file|directory] [--dry-run]"
----
-
-# /agileflow:migrate:codemods
-
-Generate AST-based codemods for automated code transformations. Preview changes with dry-run before applying, with full rollback support.
-
----
-
-## Quick Reference
-
-```
-/agileflow:migrate:codemods "CommonJS to ESM" src/            # Generate CJS->ESM codemod
-/agileflow:migrate:codemods "class to function components"     # React class->function
-/agileflow:migrate:codemods "enzyme to testing-library"        # Test migration
-/agileflow:migrate:codemods "require to import" --dry-run      # Preview only
-/agileflow:migrate:codemods "update API v2 to v3" src/api/     # API migration
-```
-
----
-
-## How It Works
-
-1. **Analyze transformation** - Understand the before/after patterns
-2. **Scan target files** - Find all instances of the "before" pattern
-3. **Generate transformation** - Create the codemod logic (using regex, AST, or direct edit)
-4. **Dry-run preview** - Show what would change without modifying files
-5. **Apply changes** - Execute the transformation with backup
-6. **Verify** - Run tests to confirm nothing broke
-
----
-
-## Step-by-Step Process
-
-### STEP 1: Parse Arguments
-
-```
-TRANSFORMATION = description of the transformation
-TARGET = file or directory (default: current directory)
-DRY_RUN = --dry-run flag present (default: false, always dry-run first)
-```
-
-### STEP 2: Analyze Transformation
-
-Delegate to `agileflow-refactor` agent:
-- Understand the source and target patterns
-- Identify edge cases and exceptions
-- Determine if transformation is safe (reversible, no logic change)
-
-### STEP 3: Find All Instances
-
-Scan target files for the source pattern:
-- Count total instances
-- Group by file
-- Flag edge cases that need manual review
-
-### STEP 4: Generate Codemod
-
-Create the transformation logic:
-
-```markdown
-## Codemod: {Transformation Name}
-
-**Source Pattern**:
-\`\`\`javascript
-{before pattern}
-\`\`\`
-
-**Target Pattern**:
-\`\`\`javascript
-{after pattern}
-\`\`\`
-
-**Files Affected**: {N} files, {M} instances
-**Edge Cases**: {list of cases needing manual review}
-**Safety**: {safe/review-needed}
-```
-
-### STEP 5: Dry-Run Preview
-
-**ALWAYS show dry-run first** before applying:
-
-```
-Codemod Preview: "CommonJS to ESM"
-═══════════════════════════════════
-
-Files affected: 15
-Total transformations: 42
-Edge cases (manual review): 3
-
-Example transformation:
-  src/utils.js:1
-  - const { readFile } = require('fs');
-  + import { readFile } from 'fs';
-
-  src/utils.js:5
-  - module.exports = { helper };
-  + export { helper };
-
-Edge cases (skipped):
-  src/dynamic-loader.js:12 - dynamic require()
-  src/config.js:8 - conditional require()
-  src/legacy.js:1 - require with side effects
-
-Apply transformations? [Y/n/review-edge-cases]
-```
-
-### STEP 6: Apply and Verify
-
-After user approval:
-1. Create git stash or backup
-2. Apply transformations file by file
-3. Run linter to fix formatting
-4. Run tests to verify
-5. Show summary of changes
-
-### STEP 7: Offer Next Steps
-
-```
-Codemod applied: [N] transformations in [M] files. [E] edge cases need manual review.
-
-Options:
-- Run tests to verify changes (Recommended)
-- Review edge cases manually
-- Undo all changes (git checkout)
-- Continue with next migration step
-```
-
----
-
-## Common Codemods
-
-| Transformation | Description |
-|---------------|-------------|
-| CJS to ESM | `require()` -> `import`, `module.exports` -> `export` |
-| Class to function | React class components -> function components with hooks |
-| Enzyme to RTL | Enzyme test assertions -> React Testing Library |
-| PropTypes to TypeScript | Runtime PropTypes -> TypeScript interfaces |
-| Callbacks to async/await | Callback-based code -> async/await |
-| var to const/let | `var` declarations -> `const`/`let` |
-
----
-
-## Related Commands
-
-- `/agileflow:migrate:scan` - Detect migration opportunities
-- `/agileflow:migrate:plan` - Generate migration roadmap
-- `/agileflow:migrate:validate` - Post-migration verification
-- `/agileflow:verify` - Run tests after transformation

package/src/core/commands/migrate/plan.md

@@ -1,131 +0,0 @@
----
-description: Generate step-by-step migration roadmap with risk assessment, rollback strategy, and execution order from scan results
-argument-hint: "[scan-report|package-name] [SCOPE=full|incremental]"
----
-
-# /agileflow:migrate:plan
-
-Generate a detailed migration plan with step-by-step execution order, risk assessment, rollback strategies, and dependency mapping from scan results or specific upgrade targets.
-
----
-
-## Quick Reference
-
-```
-/agileflow:migrate:plan                                    # Plan from latest scan report
-/agileflow:migrate:plan react                              # Plan React upgrade specifically
-/agileflow:migrate:plan next@15                            # Plan Next.js 15 migration
-/agileflow:migrate:plan . SCOPE=incremental                # Incremental migration (phase by phase)
-/agileflow:migrate:plan typescript@5.5                     # Plan TypeScript upgrade
-```
-
----
-
-## How It Works
-
-1. **Read scan results** or analyze specific upgrade target
-2. **Map dependencies** between migration steps
-3. **Assess risk** for each step (data loss, downtime, breaking changes)
-4. **Design rollback** strategy for each step
-5. **Order execution** by dependency and risk (safest first)
-6. **Estimate effort** per step
-
----
-
-## Step-by-Step Process
-
-### STEP 1: Parse Arguments
-
-```
-TARGET = scan report path, package name, or package@version
-SCOPE = full (all at once) or incremental (phased)
-```
-
-### STEP 2: Research Migration Path
-
-Delegate to `agileflow-research` agent:
-- Read official migration guides for the target upgrade
-- Find known issues and workarounds
-- Check community experience (GitHub issues, blog posts)
-- Identify breaking changes between current and target versions
-
-### STEP 3: Map Dependencies
-
-Build a dependency graph of migration steps:
-- Which steps must happen before others
-- Which steps can run in parallel
-- Which steps affect shared code
-
-### STEP 4: Assess Risk
-
-For each migration step:
-
-| Risk Level | Criteria |
-|------------|----------|
-| **High** | Data migration, schema changes, auth changes |
-| **Medium** | API changes, dependency swaps, config changes |
-| **Low** | Syntax updates, import changes, type updates |
-
-### STEP 5: Generate Migration Plan
-
-```markdown
-# Migration Plan: {Target}
-
-**Generated**: {date}
-**Current State**: {current versions/patterns}
-**Target State**: {target versions/patterns}
-**Estimated Effort**: {total estimate}
-**Risk Level**: {overall risk}
-
-## Pre-Migration Checklist
-- [ ] Full test suite passing
-- [ ] Database backup created
-- [ ] Feature flags for gradual rollout
-- [ ] Rollback procedure documented
-
-## Phase 1: {Name} (Risk: Low)
-### Step 1.1: {Action}
-- **What**: {specific change}
-- **Files affected**: {list}
-- **Risk**: {description}
-- **Rollback**: {how to undo}
-- **Verification**: {how to confirm success}
-
-### Step 1.2: {Action}
-...
-
-## Phase 2: {Name} (Risk: Medium)
-...
-
-## Phase 3: {Name} (Risk: High)
-...
-
-## Post-Migration Verification
-- [ ] All tests passing
-- [ ] No deprecated API warnings
-- [ ] Performance benchmarks stable
-- [ ] Monitoring shows no regressions
-```
-
-Save to `docs/08-project/migrations/plan-{target}-{YYYYMMDD}.md`
-
-### STEP 6: Offer Next Steps
-
-```
-Migration plan generated: [N] phases, [M] steps. Estimated effort: [estimate].
-
-Options:
-- Generate codemods for Phase 1 (Recommended)
-- Create stories from migration steps
-- Review plan in detail
-- Save plan and done
-```
-
----
-
-## Related Commands
-
-- `/agileflow:migrate:scan` - Detect migration opportunities
-- `/agileflow:migrate:codemods` - Generate AST-based codemods
-- `/agileflow:migrate:validate` - Post-migration verification
-- `/agileflow:research:ask` - Deep research on specific migration topics

package/src/core/commands/migrate/scan.md

@@ -1,114 +0,0 @@
----
-description: Detect deprecated APIs, outdated patterns, breaking dependency changes, and migration opportunities in your codebase
-argument-hint: "[file|directory] [FOCUS=deps|patterns|apis|all]"
----
-
-# /agileflow:migrate:scan
-
-Scan the codebase for migration opportunities - deprecated APIs, outdated patterns, breaking dependency changes, and version-specific issues that need attention.
-
----
-
-## Quick Reference
-
-```
-/agileflow:migrate:scan                        # Scan entire project
-/agileflow:migrate:scan src/                   # Scan specific directory
-/agileflow:migrate:scan . FOCUS=deps           # Focus on dependency changes only
-/agileflow:migrate:scan . FOCUS=patterns       # Focus on outdated code patterns
-/agileflow:migrate:scan . FOCUS=apis           # Focus on deprecated API usage
-```
-
----
-
-## How It Works
-
-1. **Dependency analysis**: Check package.json for outdated deps, breaking version jumps, deprecated packages
-2. **Pattern detection**: Find outdated coding patterns (old React class components, CommonJS in ESM projects, etc.)
-3. **API deprecation**: Find usage of deprecated APIs (Node.js, browser, framework-specific)
-4. **Version incompatibility**: Detect code that won't work with newer versions of dependencies
-5. **Migration urgency**: Score each finding by urgency (security fix, breaking change, deprecation timeline)
-
----
-
-## Step-by-Step Process
-
-### STEP 1: Parse Arguments
-
-```
-TARGET = first argument or current directory
-FOCUS = all (default) or deps|patterns|apis
-```
-
-### STEP 2: Analyze Dependencies
-
-Use the `agileflow-devops` agent to:
-- Run `npm outdated` or equivalent
-- Check for deprecated packages (`npm info <pkg> deprecated`)
-- Identify major version jumps with breaking changes
-- Check for known vulnerabilities (`npm audit`)
-
-### STEP 3: Scan for Outdated Patterns
-
-Use the `agileflow-refactor` agent to find:
-- Deprecated framework patterns (React class components, Vue Options API in Vue 3+, etc.)
-- Old module systems (CommonJS `require()` in ESM projects)
-- Deprecated Node.js APIs (`fs.exists`, `url.parse`, `new Buffer()`)
-- Old test patterns (enzyme vs testing-library)
-- Legacy build tool configurations
-
-### STEP 4: Detect Deprecated API Usage
-
-Use the `agileflow-research` agent to:
-- Check framework changelogs for deprecated features
-- Find deprecated browser APIs (e.g., `document.write`, synchronous XHR)
-- Identify Node.js deprecated APIs by version
-
-### STEP 5: Generate Scan Report
-
-Output a prioritized list of migration opportunities:
-
-```markdown
-# Migration Scan Report
-
-**Generated**: {date}
-**Target**: {directory}
-**Total Opportunities**: {N}
-
-## Critical (Security/Breaking)
-| Package/Pattern | Current | Target | Risk | Effort |
-|-----------------|---------|--------|------|--------|
-| {name} | {version} | {version} | {desc} | {est} |
-
-## High Priority (Deprecation Deadline)
-...
-
-## Medium Priority (Tech Debt)
-...
-
-## Low Priority (Improvements)
-...
-```
-
-Save to `docs/08-project/migrations/scan-{YYYYMMDD}.md`
-
-### STEP 6: Offer Next Steps
-
-```
-Scan complete: [N] migration opportunities found ([critical] critical, [high] high priority).
-
-Options:
-- Generate migration plan for critical items (Recommended)
-- Create stories for all findings
-- Re-scan with different focus
-- Save report and done
-```
-
----
-
-## Related Commands
-
-- `/agileflow:migrate:plan` - Generate step-by-step migration roadmap
-- `/agileflow:migrate:codemods` - Generate AST-based codemods
-- `/agileflow:migrate:validate` - Post-migration verification
-- `/agileflow:packages` - Dependency management

package/src/core/commands/migrate/validate.md

@@ -1,119 +0,0 @@
----
-description: Post-migration verification - run tests, check for deprecated usage, validate types, and confirm migration completeness
-argument-hint: "[migration-plan|package-name] [--strict]"
----
-
-# /agileflow:migrate:validate
-
-Run comprehensive post-migration verification to confirm the migration was successful - tests pass, no deprecated APIs remain, types check, and no regressions introduced.
-
----
-
-## Quick Reference
-
-```
-/agileflow:migrate:validate                                # Validate latest migration
-/agileflow:migrate:validate react                          # Validate React migration
-/agileflow:migrate:validate next@15                        # Validate Next.js 15 migration
-/agileflow:migrate:validate . --strict                     # Strict mode - zero warnings
-```
-
----
-
-## How It Works
-
-1. **Run test suite** - Full test run to catch regressions
-2. **Re-scan for deprecated usage** - Verify no deprecated APIs remain
-3. **Type check** - Run TypeScript/type checker for type errors
-4. **Lint check** - Run linter for new issues
-5. **Build check** - Verify production build succeeds
-6. **Generate validation report** - Pass/fail with details
-
----
-
-## Step-by-Step Process
-
-### STEP 1: Parse Arguments
-
-```
-TARGET = migration plan path, package name, or current directory
-STRICT = --strict flag (zero warnings tolerance)
-```
-
-### STEP 2: Run Validation Checks
-
-Execute all checks and collect results:
-
-| Check | Command | Pass Criteria |
-|-------|---------|--------------|
-| Tests | `npm test` | All passing |
-| Type check | `npx tsc --noEmit` | No errors |
-| Lint | `npm run lint` | No errors (warnings OK unless strict) |
-| Build | `npm run build` | Exits 0 |
-| Deprecated scan | Re-run `/agileflow:migrate:scan` | No critical findings |
-
-### STEP 3: Compare Before/After
-
-If a migration plan exists, compare:
-- Test count: same or more (not fewer)
-- Build size: within 10% (flag large increases)
-- Type errors: zero new errors
-- Deprecated usage: reduced to zero for migrated items
-
-### STEP 4: Generate Validation Report
-
-```markdown
-# Migration Validation Report
-
-**Generated**: {date}
-**Migration**: {target}
-**Status**: {PASS | PARTIAL | FAIL}
-
-## Check Results
-
-| Check | Status | Details |
-|-------|--------|---------|
-| Tests | {pass/fail} | {N} passing, {M} failing |
-| Types | {pass/fail} | {N} errors |
-| Lint | {pass/fail} | {N} errors, {M} warnings |
-| Build | {pass/fail} | Build size: {N} |
-| Deprecated scan | {pass/fail} | {N} remaining items |
-
-## Failures (if any)
-
-### Test Failures
-{list of failing tests with details}
-
-### Type Errors
-{list of new type errors}
-
-### Remaining Deprecated Usage
-{list of deprecated items still in codebase}
-
-## Verdict
-
-{Overall assessment and recommended next steps}
-```
-
-Save to `docs/08-project/migrations/validation-{YYYYMMDD}.md`
-
-### STEP 5: Offer Next Steps
-
-```
-Migration validation: [STATUS]. [N]/[M] checks passed.
-
-Options:
-- Fix failing tests (Recommended)
-- Fix remaining deprecated usage
-- Accept partial migration and create stories for remaining work
-- Mark migration as complete
-```
-
----
-
-## Related Commands
-
-- `/agileflow:migrate:scan` - Detect migration opportunities
-- `/agileflow:migrate:plan` - Generate migration roadmap
-- `/agileflow:migrate:codemods` - Generate AST-based codemods
-- `/agileflow:verify` - Run project tests