Ultimate Fix-All - Quick Start Guide
February 11, 2026 ยท View on GitHub
๐ Get Started in 30 Seconds
Run via GitHub UI
- Go to Actions tab
- Click Ultimate Fix-All Orchestrator
- Click Run workflow button
- Click Run workflow (accept defaults)
- โ 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:
| # | Stage | Fixes |
|---|---|---|
| 0 | Preflight | Kill switch, git integrity, health check |
| 1 | Foundation | Git config, package.json, .gitignore |
| 2 | Code Quality | Prettier, ESLint, TypeScript |
| 3 | Workflows | Actions, permissions, agents |
| 4 | Security | Vulnerabilities, dependencies |
| 5 | Documentation | Markdown, YAML, index |
| 6 | Testing | Test suite, build validation |
| 7 | Summary | Health 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
- Go to Actions tab
- Click on the running workflow
- Watch stages complete in real-time
- Check logs for details
After Completion
- View summary at bottom of workflow
- Check
_OPS/AUDIT/ultimate-fix-all-*.md - Review health score
- 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
truefor comprehensive cleanup,falsefor efficiency
skip_validation
- Default: false
- Options: true/false
- Purpose: Skip testing stage for faster execution
- Recommendation: Use
false(safer), only usetrueif time-critical
create_summary_pr
- Default: true
- Options: true/false
- Purpose: Create PR with all fixes at the end
- Recommendation: Use
truefor visibility,falsefor 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:
- Go to Actions tab
- Click failed workflow
- Expand failed stage
- 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
| Score | Status | Action |
|---|---|---|
| 90-100 | โ Excellent | Maintain |
| 70-89 | ๐ข Good | Monitor |
| 50-69 | ๐ก Fair | Run ultimate fix-all |
| 30-49 | ๐ Poor | Force full run |
| 0-29 | ๐ด Critical | Manual investigation + full run |
๐ Quick Links
๐ก Pro Tips
- Schedule Wisely - Runs at 8 AM & 8 PM UTC by default
- Monitor Health - Set alerts for score < 70
- Trust the System - Most issues auto-resolve
- Manual Last - Let automation run first
- Check Audit Logs - Full history in
_OPS/AUDIT/
๐ Learn More
New to this system?
- Read the Quick Start (you're here!)
- Run it once with defaults
- Check the results
- Read Full Documentation
- 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