Ultimate Fix-All - Quick Start Guide

February 11, 2026 ยท View on GitHub

๐Ÿš€ Get Started in 30 Seconds

Run via GitHub UI

  1. Go to Actions tab
  2. Click Ultimate Fix-All Orchestrator
  3. Click Run workflow button
  4. Click Run workflow (accept defaults)
  5. โœ… Done! Watch it fix everything

Run via CLI

# Simple - use defaults
gh workflow run ultimate-fix-all.yml

# Advanced - custom options
gh workflow run ultimate-fix-all.yml \
  -f max_cycles=10 \
  -f force_full_run=true

๐Ÿ“Š What It Does

The Ultimate Fix-All Orchestrator runs 8 comprehensive stages:

#StageFixes
0PreflightKill switch, git integrity, health check
1FoundationGit config, package.json, .gitignore
2Code QualityPrettier, ESLint, TypeScript
3WorkflowsActions, permissions, agents
4SecurityVulnerabilities, dependencies
5DocumentationMarkdown, YAML, index
6TestingTest suite, build validation
7SummaryHealth score, audit log, PR

โฑ๏ธ How Long?

  • Minimum: ~10 minutes (no issues found)
  • Typical: ~15-20 minutes (normal fixes)
  • Maximum: ~30 minutes (comprehensive cleanup)

๐ŸŽฏ When to Use

โœ… Use It When:

  • Repository health score < 80
  • After major changes/refactoring
  • Before important releases
  • Mysterious issues appearing
  • Need comprehensive cleanup

โญ๏ธ Skip It When:

  • Quick fix needed (use agents instead)
  • Currently developing/testing
  • Kill switch is active
  • Only one file needs fixing

๐Ÿ“ˆ Check Results

During Execution

  1. Go to Actions tab
  2. Click on the running workflow
  3. Watch stages complete in real-time
  4. Check logs for details

After Completion

  1. View summary at bottom of workflow
  2. Check _OPS/AUDIT/ultimate-fix-all-*.md
  3. Review health score
  4. Check for created PR

๐Ÿ”’ Safety Features

  • โœ… Kill Switch - Stops immediately if activated
  • โœ… Continue-on-Error - One failure doesn't stop others
  • โœ… Audit Logging - Full transparency
  • โœ… Rate Limited - Only 2x per day automatically
  • โœ… Rollback Ready - Git history preserved

โš™๏ธ Configuration Options

max_cycles

  • Default: 5
  • Range: 1-20
  • Purpose: How many times to retry if issues remain
  • Recommendation: Use default unless you have persistent issues

force_full_run

  • Default: false
  • Options: true/false
  • Purpose: Run all stages even if no issues detected
  • Recommendation: Use true for comprehensive cleanup, false for efficiency

skip_validation

  • Default: false
  • Options: true/false
  • Purpose: Skip testing stage for faster execution
  • Recommendation: Use false (safer), only use true if time-critical

create_summary_pr

  • Default: true
  • Options: true/false
  • Purpose: Create PR with all fixes at the end
  • Recommendation: Use true for visibility, false for automated merge

๐ŸŽจ Examples

Basic Usage

# Run with all defaults (recommended for most cases)
gh workflow run ultimate-fix-all.yml

Major Cleanup

# Force full run with extra cycles
gh workflow run ultimate-fix-all.yml \
  -f max_cycles=10 \
  -f force_full_run=true

Quick Validation

# Fast run without validation (not recommended for production)
gh workflow run ultimate-fix-all.yml \
  -f skip_validation=true \
  -f max_cycles=1

Silent Fixes

# Fix everything without creating PR
gh workflow run ultimate-fix-all.yml \
  -f create_summary_pr=false

๐Ÿ” Troubleshooting

"Workflow not running"

# Check kill switch
cat _OPS/SAFETY/KILL_SWITCH.json

# If active, deactivate:
echo '{"active": false}' > _OPS/SAFETY/KILL_SWITCH.json
git add _OPS/SAFETY/KILL_SWITCH.json
git commit -m "Deactivate kill switch"
git push

"Some stages failing"

Normal! The workflow uses continue-on-error, so:

  • โœ… Failures don't stop other stages
  • โœ… Maximum fixes are applied
  • โœ… Issues are logged for review

Check logs:

  1. Go to Actions tab
  2. Click failed workflow
  3. Expand failed stage
  4. Read error messages

"Health score not improving"

Try:

# Force comprehensive cleanup
gh workflow run ultimate-fix-all.yml \
  -f force_full_run=true \
  -f max_cycles=10

Then check:

  • Are there manual changes interfering?
  • Are dependencies outdated?
  • Are there test failures?

๐Ÿ“Š Health Score Guide

ScoreStatusAction
90-100โœ… ExcellentMaintain
70-89๐ŸŸข GoodMonitor
50-69๐ŸŸก FairRun ultimate fix-all
30-49๐ŸŸ  PoorForce full run
0-29๐Ÿ”ด CriticalManual investigation + full run

๐Ÿ’ก Pro Tips

  1. Schedule Wisely - Runs at 8 AM & 8 PM UTC by default
  2. Monitor Health - Set alerts for score < 70
  3. Trust the System - Most issues auto-resolve
  4. Manual Last - Let automation run first
  5. Check Audit Logs - Full history in _OPS/AUDIT/

๐ŸŽ“ Learn More

New to this system?

  1. Read the Quick Start (you're here!)
  2. Run it once with defaults
  3. Check the results
  4. Read Full Documentation
  5. Customize as needed

Advanced user?

  • Customize schedule in workflow file
  • Add custom fix stages
  • Integrate with monitoring
  • Set up alerts

Need Help? Check Troubleshooting or read the Full Guide