Back to Dashboard
Documentation/Features/Reform Wizard

Reform Wizard

Automated repository refactoring and rebranding

Reform Wizard

The Reform Wizard is an AI-powered tool for automated repository refactoring and rebranding. Transform existing projects with intelligent code updates while maintaining functionality.

Overview

The Reform Wizard helps you:

  • Rebrand projects: Update names, authors, and branding
  • Refactor code: Modernize patterns and structure
  • Update documentation: README, LICENSE, and docs
  • Migrate configurations: Package.json, configs, etc.
  • Preview changes: See diffs before applying

Getting Started

Basic Workflow

  1. Upload or Connect: Add your project files
  2. Configure: Set new project details
  3. Select Files: Choose files to transform
  4. Preview: Review AI-generated changes
  5. Apply: Download the refactored project

Accessing Reform Wizard

The Reform Wizard is integrated into the ReformCode platform. While the main tabs focus on code editing and generation, Reform Wizard functionality is available for:

  • Repository rebranding
  • Bulk file transformations
  • Project migrations

Configuration Options

Project Identity

New Project Name: The name for your refactored project

  • Used in package.json, README, etc.
  • Updates all references

Author Information:

  • Author name
  • Email
  • Website/URL

Description: New project description

Branding Elements

Replace Throughout:

  • Project name occurrences
  • Author/company names
  • URLs and links
  • License holder

Preserve:

  • Third-party references
  • Library names
  • External URLs

Tech Stack Selection

Choose your target stack:

  • Frontend: React, Vue, Angular, Svelte
  • Backend: Node, Python, Go, Rust
  • Styling: Tailwind, CSS Modules, Styled Components
  • Build: Vite, Webpack, Next.js

File Selection

Automatic Detection

Reform Wizard detects relevant files:

  • Configuration files (package.json, tsconfig.json)
  • Documentation (README.md, CHANGELOG.md)
  • License files
  • Source code with branding references

Manual Selection

Choose specific files:

  1. Browse the file tree
  2. Check files to include
  3. Uncheck files to skip

Bulk Selection

  • Select All: Include everything
  • Select by Type: All .md files, all configs
  • Invert Selection: Flip selections

AI Refactoring

What Gets Updated

Documentation Files:

  • Project name and description
  • Author information
  • Badge URLs
  • Installation instructions
  • Usage examples

Configuration Files:

  • package.json name and author
  • License files
  • CI/CD configurations
  • Environment examples

Source Code (when enabled):

  • Comments and documentation
  • String literals with project name
  • Copyright notices

AI Intelligence

The AI understands context:

  • Won't change external library names
  • Preserves code functionality
  • Maintains consistent style
  • Handles edge cases

Preview Changes

Diff View

Review all changes before applying:

  • Side-by-side comparison
  • Inline diff view
  • Line-by-line changes
  • Syntax highlighting

File-by-File Review

  1. Select a file from the list
  2. See original vs. modified
  3. Accept or reject changes
  4. Move to next file

Bulk Actions

  • Accept All: Apply all changes
  • Reject All: Discard all changes
  • Accept Selected: Apply chosen files

Applying Changes

Download Options

ZIP Package:

  • Complete refactored project
  • Ready to use locally
  • Includes all selected files

Individual Files:

  • Download specific files
  • Useful for selective updates

GitHub Export

Push refactored project to GitHub:

  1. Click Push to GitHub
  2. Choose new or existing repo
  3. Confirm and push

Use Cases

Rebranding a Fork

Transform a forked project for your own use:

Original: awesome-template
New: my-company-app
Author: Your Name

Project Migration

Move to a new organization:

Old: personal/my-project
New: company/official-project
Update all references

Boilerplate Customization

Customize a starter template:

Template: next-starter
Your App: product-dashboard
Add your branding

License Updates

Change licensing:

Original: MIT (Original Author)
New: MIT (Your Company)
Update all copyright notices

Best Practices

Before Starting

  1. Backup original: Keep a copy of the original
  2. Review scope: Know what you want to change
  3. Prepare details: Have new names/info ready

During Refactoring

  1. Start small: Test with a few files first
  2. Review carefully: Check all diffs
  3. Test incrementally: Verify changes work

After Applying

  1. Build test: Ensure project builds
  2. Run tests: Verify functionality
  3. Manual review: Check edge cases
  4. Version control: Commit with clear message

Credit Usage

ActionCredits
Small project (< 20 files)5
Medium project (20-50 files)7
Large project (50+ files)10

Troubleshooting

"File not recognized"

  • Check file encoding (UTF-8 preferred)
  • Ensure file isn't binary
  • Try different file type

"Changes incomplete"

  • Complex code may need manual review
  • Try processing in smaller batches
  • Use a more powerful AI model

"Build fails after refactor"

  • Check for missed references
  • Review import statements
  • Verify configuration files

"Name still appears"

  • Check generated/cached files
  • Review build output directories
  • Look for hardcoded strings

Limitations

What It Can't Do

  • Rename functions/variables in code logic
  • Refactor architecture
  • Change programming languages
  • Update binary files

Manual Steps May Be Needed

  • Complex regex replacements
  • Database schema changes
  • External service configurations
  • API endpoint updates

Next Steps: