---

name: autonomous-mode description: Autonomous codebase improvement mode that continuously analyzes and fixes issues. Use when the user wants Claude to run in a self-directed loop to improve code quality, fix bugs, refactor, or make architectural improvements without requiring manual prompts for each change. Triggers on phrases like "autonomous mode", "continuous improvement", "auto-fix", "improvement loop", or requests to automatically improve the codebase.

Autonomous Mode

Continuously improve the codebase through an autonomous analysis-fix-test-commit loop.

The Loop

Execute this cycle until stopped:

1. Discover - Find files to analyze
2. Analyze - Deep-dive into one file for issues
3. Fix - Make the most impactful improvement
4. Test - Run tests to verify the fix
5. Commit - Commit if tests pass (one fix per commit)
6. Log - Record progress in .claude-improvements.log
7. Continue - Say "NEXT" and return to step 1

Discovery Phase

Copy# Find source files (adjust extensions for the project)
find . -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.php" -o -name "*.py" \) \
  -not -path "*/node_modules/*" -not -path "*/vendor/*" -not -path "*/.git/*" | head -30

Track analyzed files in .claude-improvements.log to avoid re-analyzing.

Analysis Checklist

For each file, check for:

• Critical: Syntax errors, undefined methods/variables, SQL injection, XSS
• High: Missing error handling, type mismatches, security issues
• Medium: Code duplication, missing validation, poor naming
• Low: Style issues, missing docs, TODO comments

Prioritize by impact. Fix the most critical issue first.

Fix Rules

• One fix per commit - Keep changes atomic and reviewable
• Minimal changes - Change only what's necessary
• Preserve behavior - Don't break existing functionality
• Run tests before committing - Never commit failing code

Commit Format

Copygit add <files>
git commit -m "fix(<scope>): <description>

- What was wrong
- How it was fixed
- Impact of the change"

Progress Logging

Append to .claude-improvements.log:

Copy[YYYY-MM-DD HH:MM] FILE: path/to/file.ts
  ISSUE: Description of the issue found
  FIX: Description of the fix applied
  COMMIT: abc1234
  STATUS: PASS/FAIL
---

Escalation

When all files have been analyzed:

1. Re-run static analysis tools (linters, type checkers)
2. Look for cross-file issues (unused exports, circular deps)
3. Consider architectural improvements
4. Update dependencies if outdated
5. Improve test coverage

Stop Conditions

Stop the loop when:

• User says "stop" or "pause"
• A critical error occurs that needs human input
• All improvements are exhausted (rare)

Start Command

Begin with:

Copyecho "=== AUTONOMOUS MODE STARTED ===" >> .claude-improvements.log
echo "[$(date '+%Y-%m-%d %H:%M')] Session started" >> .claude-improvements.log

Then immediately enter the loop. Say "NEXT" after each cycle to continue.