Skip to main content
aislop fix is the deterministic cleanup layer. It applies mechanical fixes first - unused imports, narrative comments, formatting, dead code - and can still print or open a structured prompt for older agent handoff flows. For the full local repair workflow with worktrees, provider setup, verification, sessions, and optional PR publishing, use aislop agent.

​
Fix workflow

Work through the stages in order to reach 100/100 with the least disruption to your codebase:
1

Run a plain scan to see everything

Before touching anything, get the full picture.
2

Apply only reversible fixes with --safe

Start conservatively. --safe restricts the run to fixes that cannot change behaviour: unused-import removal, import merging, narrative-comment removal, and formatting. Apply these, review the diff, and commit.
3

Run the standard auto-fixer

Without --safe, aislop also clears console-log leftovers, removes dead code, and runs lint autofixes. Review the diff before committing.
4

Run aggressive fixes with --force

--force adds dependency auditing, framework alignment checks, and unused-file removal. These are more disruptive, so review the diff carefully.
5

Hand off remaining issues to your agent

For the full local repair loop, run aislop agent. For prompt-based handoff, pass the remaining diagnostics to your coding agent with full diagnostic information:
6

Verify with a final scan

Confirm everything is resolved.

​
Flags

​
boolean
Show detailed progress for each fix operation as it runs, including which files are modified and which rules are being resolved.
​
boolean
Run aggressive fixes in addition to standard ones. This includes dependency auditing, framework dependency alignment, and unused-file removal. Changes here are more likely to affect behaviour—review the diff before committing.
​
boolean
Restrict the run to reversible fixes only. Safe mode applies:
  • Unused-import removal
  • Import merging
  • Narrative-comment removal
  • Formatting
Anything that deletes code or rewrites behaviour—console removal, dead-code elimination, lint autofixes, unused-declaration pruning, and dependency changes—is skipped. A --safe run is designed to be “apply and commit” without review.
​
boolean
Print an agent-ready prompt to stdout describing the remaining issues, without opening any specific agent. Use this flag when you want to paste the prompt into any tool or inspect it first.

​
Prompt handoff flags

When auto-fix can’t resolve an issue and you do not want the full aislop agent workflow, pass the remaining diagnostics to your coding agent. Each flag opens that agent and provides the structured prompt automatically. Use --prompt / -p if you prefer an agent-agnostic output you can paste anywhere.
Use --prompt (-p) to print the agent handoff prompt without opening any specific tool. You can then paste it into any agent, share it with a teammate, or inspect the diagnostics before deciding what to do next.

​
What —safe restricts

--safe is designed for situations where you want to improve the score with zero risk of introducing bugs. The table below shows what runs and what is skipped:

​
Common examples