Free hiring tool
Review a Candidate's Code or GitHub
Plain-English review of a candidate's GitHub repo or code sample for non-technical hirers: quality signals, authorship checks, a risky-function trace and questions that reveal who really wrote it.
What it produces
- A three-sentence bottom line you can read aloud to a cofounder.
- An authorship table: fork or tutorial, who committed, history shape, and any sign of an employer's confidential code.
- Up to eight code signals, each with the file it came from, what it suggests and a confidence level, with jargon explained.
- Authorship questions naming a specific file or decision, each with "a real author will..." and "a bluff sounds like...".
- A 10-minute screen-share plan with one small change request that authors find in seconds.
- The limits of what a code sample can tell you.
Worked example
From the Code Sample Review playbook this tool uses.
From a run on a fictional example. The input: a non-technical founder hiring a first engineer pasted a candidate's README, file list, eight commits, part of a payments file and a public .env file, and asked whether 60 contributions a year "seems low".
| Who committed | Almost all commits shown are by "Kit Brannagan". One is "Merge pull request #3 from jpwellsby-example/calendar-ui", with the work itself, "calendar month view + drag to reschedule" (Feb 11), by J.P. Wellsby. | A second person built the calendar screen and Kit accepted it into the project. That part is not his. Ask who J.P. is and which other parts, if any, they touched. |
What it needs
| Input | What to give it |
|---|---|
| Code or repooptional | Paste the code, file excerpts, README and commit history (or describe the repo) |
| Roleoptional | Role and level you are hiring for |
Call it from your assistant
In any assistant connected to Ruzora's MCP server, the tool is review_code_sample. Your assistant fills the arguments from the conversation; this is the shape:
{
"code_or_repo": "..."
}Frequently asked questions
- Is "Review a Candidate's Code or GitHub" free?
- Yes, it is free. Run it in Claude, ChatGPT or any assistant that connects to Ruzora's MCP server, with no API key.
- What does "Review a Candidate's Code or GitHub" need from me?
- Code or repo (optional): Paste the code, file excerpts, README and commit history (or describe the repo). Role (optional): Role and level you are hiring for.
- How does "Review a Candidate's Code or GitHub" work?
- The tool hands your details and Ruzora's Code Sample Review playbook to the AI you run it in, which follows the playbook to write the result. Ruzora's server does not run a model for it.
- Does it make the hiring decision?
- This organizes evidence for you. It is not a hiring decision: you make the call.