praisonai code — no separate PR, no writes to your files.
Two slash commands run inside the praisonai code interactive session:
/code-review [file] [--staged]— reviews the working-tree diff for bugs, logic errors, and edge cases./security-review [file] [--staged]— same pipeline with a security rubric: injection, authz, secrets, deserialization, path traversal, SSRF, and crypto.
review agent preset. Its tool set excludes write and command-execution tools, so the command cannot touch your files even if the model tries.
Quick Start
1
Launch a session
Start
praisonai code in a git repository with uncommitted changes:2
Review the working-tree diff
Type
/code-review — the agent reads your uncommitted diff and reports findings:3
Audit for security issues
Swap in the security rubric with
/security-review:Agent with read-only instructions:
You don’t build this agent yourself —
/code-review and /security-review ship it for you and feed it the diff. The snippet above shows what the command does under the hood.How It Works
/code-review collects the diff, wraps it in a review rubric, and runs it against the read-only agent — findings come straight back to the REPL.
Common Patterns
Review before you stage. Run/code-review on the working tree, apply fixes, then re-check:
--staged to scope the review to staged changes:
shlex, so /code-review "src/my dir/app.py" works. Multiple positional paths are rejected with a usage message.
User Interaction Flow
A typical loop: finish an edit, review, fix, then security-check before staging.1
Finish an edit
Make your changes in the session as usual.
2
Review for bugs
Type
/code-review — the agent reports logic errors and edge cases with file:line locations.3
Apply fixes
Address the findings, then re-run
/code-review to confirm they’re gone.4
Security-check before staging
Type
/security-review — the agent audits the same diff against the security rubric before you commit.Best Practices
Run /security-review before every commit that touches auth
Run /security-review before every commit that touches auth
Auth, session, and credential code is where injection and authz flaws hide. Make
/security-review a habit before staging any change under src/auth/ or similar.Scope with --staged to review exactly what ships
Scope with --staged to review exactly what ships
The working tree may hold experiments you won’t commit. Use
--staged so the review matches the diff that will actually land.Trust the read-only guarantee on untrusted diffs
Trust the read-only guarantee on untrusted diffs
The review agent has no write or command-execution tools, and
@file tokens in the diff are never expanded. It’s safe to review diffs from sources you don’t fully trust.Treat a ReviewDiffError as a real problem
Treat a ReviewDiffError as a real problem
An empty diff prints “Working tree clean”. A
ReviewDiffError means the diff couldn’t be collected (not a repo, Git failure). Fix the underlying issue — it is never silently reported as clean.Related
Checkpoints
Snapshot and roll back workspace changes across a session.
Shell Escape
Run inline shell commands without spending a model turn.
Slash Commands
The full interactive command reference.
Permission Modes
Read-only and other enforcement modes, including
/plan.
