Dependency map
Find related modules and existing tests first.
Use cases · MCPENROUZ
AI-assisted project refactoring on your computer
Give AI the real project context and a focused task boundary. Make changes in a selected folder and verify them in the existing development environment.
Free2 devices · 100 tool calls per hour
Example task
In the allowed project, find duplicate sign-in logic. Propose a focused refactor that preserves behavior and identify relevant tests.
Your device · your permissions
Focused changes
Break large work into verifiable steps with clear outcomes.
Behavior verification
Use tests that verify the intended behavior after editing.
Get started
Establish the baseline
Check the branch, existing edits and project instructions.
Review the refactoring scope
Ask for the files, expected behavior and verification method.
Edit and verify
Enable project writes, make reviewed changes and inspect test results.
Example task
A prompt for your AI
In the allowed project, find duplicate sign-in logic. Propose a focused refactor that preserves behavior and identify relevant tests.
Permissions
Edits need write access. Git commands, builds and tests need separately enabled terminal access.
Details
Avoid unnecessary scope
Specify the relevant modules. Ask AI to follow project conventions and avoid unrelated changes.
Review the report
Request the changes, actual checks and remaining limitations. A suggested command is not a completed test.
Frequently asked questions
Can I get a plan first?
Yes. Keep access read-only and request a plan without edits.
Is deletion permission necessary?
Only if the reviewed task needs file deletion. Ordinary edits do not.
Will AI publish the code itself?
Specify authorized actions. Publishing and deployment require a separate decision and suitable access.
Next steps
MCPENROUZ · FREE
Connect a device. Start with reads.
Choose a working folder and AI client. Add writes and terminal access as your task requires.