How it works
Understand first. Change second.
Tidy Giant never starts by rewriting. It starts by learning how your app works, then proves each change is safe.
- 1
Connect GitHub
Install the Tidy Giant GitHub App on the repositories you choose. Scanning only needs read access.
- 2
Run a Tidy Scan
Giant maps the repo, checks types and lint, reviews dependencies, looks for duplication and risky patterns, and measures what tests exist. Scans never change code.
- 3
Read your results
A Tidy Score you can trace to evidence, your top issues in plain English, and a Tidy Map of how the app is wired.
- 4
Pick what to tidy
Each issue shows the risk of leaving it, the risk of changing it, the fix we recommend, and the credit estimate.
- 5
Approve the estimate
Giant reserves the maximum credits for the job and returns whatever it doesn't use.
- 6
Giant gets to work
In an isolated sandbox, on its own branch: record a baseline, add guardrail tests where they're missing, make one bounded change at a time.
- 7
A second opinion
A separate reviewer checks the diff. Then build, types, tests and browser flows run against the baseline.
- 8
Review the pull request
What changed, why, what passed, what we couldn't verify. You decide whether it merges.
Proof, not vibes
We don't just rewrite code.
We prove as much as possible that the important behavior still works. Giant records how your app behaves, makes one bounded change, and lets a separate reviewer and your own checks decide if it passes.
- ✓Never pushes to your default branch
- ✓Never merges for you
- ✓Tells you what it could not verify
Consolidate session validation
Risk: medium · 6 files changed · sample pull request
- ✓Build: pass
- ✓Typecheck: pass
- ✓Tests: 82 of 82 pass
- ✓New regression tests: 7
- ✓Independent review: approved
Verified against the available test and behavior baseline. Manual review recommended before merging.
Built it fast.
Now make it solid.
Connect a repo and see what the Giant finds. Scans never change your code.
