How can you use an AI code detector in pull request review?

Choose a review scope you can describe

A pull request may contain new code, unchanged context, and generated files. Decide which source you are reviewing before running the tool. A pasted function and a complete file are different inputs, even when both relate to the same change.

For your review notes, record the repository revision, file path, and whether you checked an excerpt or a whole file. These are notes you keep yourself; a detector result cannot supply missing project history. If you paste an excerpt, use the repository's original line numbers when discussing it so another reviewer can find the same code.

Turn a match into a code question

Is My Code AI reports a heuristic score, matched rules, and flagged lines. Start with a specific rule and its line rather than the summary score. The following prompts are review questions, not claims about the author.

• A comment is flagged: Does the comment explain a decision that the implementation does not make obvious? Does it still describe the current behavior?
• An identifier is flagged: Does the name fit the repository's conventions and make the value's role clear?
• Defensive error text is flagged: Which input triggers that branch, and does the caller handle the resulting error?

The report establishes that a configured pattern matched. It does not establish the answer to any of these questions. Read the relevant code, tests, and project conventions to answer them.

A review note you can adapt

I checked the function in [file path] at [revision]. The local report matched [rule] near [repository line]. Could you explain [specific behavior or design choice]? I am checking the implementation and its context.

Replace the bracketed fields with details from your actual review. A useful note gives the contributor a question they can answer. A score alone does not explain what needs changing.

If the pattern follows an established convention, record that context and continue the review. If you find a technical issue, describe the issue and the expected behavior directly.

Keep the merge decision grounded in the change

A code-style heuristic cannot prove authorship or identify who used an assistant. The report also does not replace review of correctness or the project's acceptance requirements. An unchanged or low score does not resolve those questions.

Review the change against its purpose, surrounding implementation, and relevant tests. Keep any discussion of development process grounded in the contributor's explanation and the evidence available in the project.

Run the local check

In Is My Code AI, you can paste code, select supported source files, or choose a local folder. Submitted code is not uploaded by this static site. The language picker supports Python, JavaScript, Java, C++, PHP, and C#.

Open the AI code detector to inspect the current input's matched rules and flagged lines.

When a matched line is a comment, see why an AI code detector flags comments before treating the pattern as meaningful.

For a separate security question, see whether an AI code detector can tell if code is safe.