Proof beats claims
A reviewed repo is not a repo where you say, “I used AI responsibly.” It is a repo where someone can see your instructions, checks, and decisions.
Your goal is simple: make it easy for a judge, mentor, or interviewer to verify that you stayed in control.
What reviewers look for
They do not need your full chat history. They need evidence that the code was reviewed before it was merged or submitted.
Show four things: project instructions for AI tools, tests or manual verification notes, no secrets in Git, and a README section explaining what AI helped with and what you checked.
Final repo checklist
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
README review section
Use simple language. Do not over-explain. Write it like something you can say in a placement interview.
AI-assisted development review
AI tools used:
- Used an AI coding assistant to draft parts of the form validation and README.
- Used AI to suggest test cases for login, empty fields, and invalid UPI ID format.
How I reviewed the output:
- Checked generated code before accepting it.
- Verified package methods against the installed dependencies.
- Ran the app locally and tested the main user flow.
- Checked that no `.env` file, API key, token, or password is committed.
Verification done:
- Signup form rejects empty name and invalid email.
- Payment screen shows an error for invalid UPI ID.
- Project starts locally using the commands below.
Known limits:
- Payment is a mock flow for the hackathon demo.
- No real money movement is implemented.Use AI for the audit
Ask your assistant to inspect the actual repo files before it comments. Give it the checklist and ask for missing proof, not praise.
Still check the answer yourself. AI tools can miss secrets, misunderstand code, or suggest risky fixes.
Prompt:
Inspect this repository before answering. Do not guess about files you have not opened.
Check whether the repo is ready for public hackathon submission.
Look for:
1. AI project instructions
2. README section explaining AI-assisted development and review
3. Tests or verification notes
4. Possible committed secrets
5. AI-generated code that needs security review
Return only missing items and exact files to fix.Do not submit vibes
A common mistake is writing “Reviewed by AI” in the README. That is weak. AI review does not replace your review.
Another mistake is making the repo public first and checking secrets later. Reverse the order. Check first, then publish.
Before you publish
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
Do this now
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done