1
See the project
Refract looks at the software as a whole, so a change in one screen can respect the rest.
Refract reads the project, finds what will get messy, and prepares a cleanup you approve. You never leave GitHub to decide.
Get started1
Refract looks at the software as a whole, so a change in one screen can respect the rest.
2
It looks for the patterns that show up when code is generated quickly: copied logic, tangled screens, leftover state, structure that won’t age well. If something sensitive was left in the code — like a credential — it tells you. It does not quietly “fix” secrets.
3
When the cleanup is safe, you get a concrete change to approve. When it isn’t, you get a clear explanation instead of a guess.
4
After you approve, Refract applies the change and looks again. Over time you can see whether the project is getting cleaner — or still shipping the mess.
The website is not a second place to accept cleanups. The decision stays next to the code.
Wait. This is not a pass.
Nothing from Refract needs you on this change.
A safe cleanup is prepared. Approve it on GitHub.
Something matters, and Refract will not change it for you. Read the explanation.
Analysis failed. Refract will say so. It will not paint a fake success.
On React and TypeScript projects, Refract is especially good at the leftovers of fast generation:
Some of that, it can clean for you. Some of that, it will only point out — on purpose. A bad automatic rewrite is worse than an honest note.
1
2
3
Connecting GitHub does not sign you into Refract, and signing into Refract does not install GitHub access. Two steps, two jobs.
No. Keep generating. Refract is the pass that keeps the result maintainable.
No. You approve. You merge.
No. Day to day, you stay on GitHub.