Tool
LockedIn AIAI-Powered Code Review Workflow
Use AI to catch bugs, enforce standards, and document code before every merge. Ship cleaner code faster.
4 steps
codingdeveloper-toolsproductivity
1
Paste code and ask for a bug review
Before opening a PR, paste the changed functions into your AI tool and ask it to find bugs, edge cases, and null-pointer risks. Fix what it finds.
Example prompt
Review this code for bugs, edge cases, and potential runtime errors. List each issue with: location (function/line), severity (critical/medium/low), what can go wrong, and a suggested fix. Code: [PASTE CODE HERE]
2
Check code style and naming conventions
Ask AI to flag style violations, inconsistent naming, and anything that does not follow your team's conventions. Paste your style guide or describe the conventions.
Example prompt
Review this code for style and consistency issues. Check: naming conventions (variables, functions, classes), function length, comment quality, magic numbers, and DRY violations. Team conventions: [DESCRIBE YOUR CONVENTIONS]. Code: [PASTE CODE HERE]
3
Generate inline documentation
Use AI to write JSDoc or docstring comments for every public function. Review them for accuracy before committing.
Example prompt
Write JSDoc comments for each function in the code below. Include: one-line summary, @param with types and descriptions, @returns with type and description, @throws if applicable, and one usage example per function. Code: [PASTE CODE HERE]
4
Write the PR description
Paste the diff and let AI write the PR description: what changed, why, how to test it. Saves 10 minutes and makes reviewers happy.
Example prompt
Write a pull request description for the following code changes. Include: Summary (2-3 sentences on what changed and why), Changes Made (bulleted list of key changes), How to Test (step-by-step testing instructions), Screenshots (placeholder if UI changed), and any Breaking Changes. Diff: [PASTE DIFF HERE]
Ready to try LockedIn AI?
Follow this playbook with the actual tool