Tool
LockedIn AIAI驱动的代码审查工作流
在每次合并前使用AI发现错误、执行标准并记录代码。更快地交付更整洁的代码。
4 steps
codingdeveloper-toolsproductivity
1
粘贴代码并请求错误审查
在打开PR之前，将更改的函数粘贴到AI工具中，让它查找错误、边界情况和空指针风险。
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
检查代码风格和命名约定
让AI标记风格违规、命名不一致以及任何不符合团队规范的内容。
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
生成内联文档
使用AI为每个公共函数编写JSDoc或docstring注释。在提交之前检查其准确性。
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
编写PR描述
粘贴差异，让AI编写PR描述：变了什么、为什么、如何测试。节省10分钟，让审查者满意。
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