Code Review via Email

Need a second pair of eyes on your code? Email it to a SlyReply code review agent and get detailed feedback in minutes — no pull request required.

Code Review Agents

Agent	Focus
DJ Debug	Bug detection, logic errors, edge cases
Code Reviewer Rex	Code quality, patterns, best practices
Security Sam	Vulnerability scanning, security anti-patterns
Refactor Rita	Code structure, DRY improvements, readability

Sending Code for Review

You can include code directly in your email body using plain text:

To: dj-debug@slyreply.ai
Subject: Review this Python function

Hi DJ, can you review this function? It is supposed to
merge two sorted lists but I am getting wrong results
for some inputs:

def merge_sorted(a, b):
    result = []
    i = j = 0
    while i < len(a) and j < len(b):
        if a[i] <= b[j]:
            result.append(a[i])
            i += 1
        else:
            result.append(b[j])
    return result

What You Get Back

The agent replies with a structured review that typically includes:

Bug identification — specific lines with issues and explanations
Fix suggestions — corrected code with inline comments
Edge case warnings — inputs that could break the function
Performance notes — time/space complexity observations
Style recommendations — naming, formatting, and idiomatic improvements

Sharing Larger Snippets

Source-code and plain-text files (.py, .js, .ts, .go, .json, .yaml, .sql, .txt, and similar) are not read as attachments — only PDFs and images are ingested natively (see Processing Email Attachments). If you attach a .py or .txt file, the reply will include an "Attachment not read" notice naming it.

For larger codebases, share the code one of these ways instead:

Paste it into the email body inside a fenced code block — this is the most reliable option and keeps the language hint intact
Convert the file to PDF before attaching if you'd rather send a file (Pro and Power read PDFs natively)
Send a screenshot of the code as an image attachment (Pro and Power read images natively) — best for short snippets

Best Practices

Describe the intent — tell the agent what the code is supposed to do
Mention the language and framework — helps the agent give idiomatic suggestions
Ask specific questions — "Is this thread-safe?" gets a better answer than "Review this"
Iterate in the thread — paste your revised code in a reply to get follow-up feedback