DoAide Code + GitHub
DoAide Code fits around a GitHub workflow at two levels: the free paste-in tools polish the code you are about to push, and the full assistant works directly on your local clones — so everything it does flows through your normal git commit and git push, reviewed by you.
Before you raise a pull request
The cheapest review comment is the one that never gets written. Before opening a PR:
- Review the change: paste the function or file you touched into the AI code review tool. Fix correctness and security findings first.
- Diff what you changed: paste the old and new version into the diff checker for a clean side-by-side you can sanity-check (or screenshot into the PR description).
- Cover it with tests: the unit test generator turns the new function into a runnable suite — PRs with tests merge faster.
- Explain it to reviewers: run Explain code on a gnarly change and paste the summary into the PR description. Reviewers love you for it.
Understanding a repository you just cloned
Dropped into an unfamiliar codebase — a new job, an open-source project, a teammate's branch? Work file by file: copy the entry point into Explain code, then follow the imports. For suspicious functions, Find bugs tells you whether that edge case you noticed is real. It is the fastest way to turn "I have no idea what this does" into a mental map.
The assistant: your clones, your commits
DoAide Code's assistant works on repositories the way you do: on a local clone. Point it at a project directory on your laptop and it reads the code, makes edits there, and leaves you to review the diff and commit. There is no GitHub OAuth app to authorize and no bot pushing to your branches — your repo never leaves your machine, and everything that reaches GitHub went through your own git push.
A typical loop: ask for a change → the assistant edits your working directory → git diff (or your editor's git pane) shows exactly what changed → commit, push, open the PR. It tries free local models first and uses Claude only when needed, so most tasks cost nothing.
Frequently asked questions
Does DoAide Code need access to my GitHub account?
No. The free tools take pasted code, and the assistant works on local clones. Nothing connects to your GitHub account, and nothing pushes on your behalf.
Can DoAide Code review a whole pull request?
The free tool reviews what you paste — for a focused PR, that is usually the changed file or functions. The assistant can work across a whole local clone, including changes spanning files.
Can I use it on private repositories?
Yes — because it works on your local clone, private repos work exactly like public ones. Only the snippets you paste into the free tools are sent for analysis.
Is there a GitHub App or bot that comments on PRs?
Not today. DoAide Code is deliberately pull-based: you bring it code and decide what to do with its answers. A PR-review bot is on the roadmap.