Product capabilities
AI code review features and workflow.
Peertic reviews pull requests against linked requirements and repository rules, publishes line-level GitHub findings, and shares verdicts in Slack. Teams can run it in their own infrastructure, inspect each review, and refine guidelines from feedback.
Pull request review
From a PR description, Peertic can use linked Jira tickets and GitHub issues as requirements context, compare acceptance criteria with changed code, and post line-level findings. Follow-up reviews revisit earlier findings; the recorded example shows where AI assistant triage was needed.
Inspect a recorded payment retry review, its test results, and follow-up →



Review engine and scan modes
File selection, related-file bundles, per-file rules, codebase context, positioning, and reflection keep reviews focused. Run reviews on working changes, branches, commits, and pull requests, or scan whole files without a diff.




Admin portal and operations
Configure Peertic, start runs, inspect saved sessions, and see what the automation server queued and why. The activity log records review posts, verdicts, and administrative changes.



Rules and project policy
Set review triggers, scope, severity thresholds, merge checks, and ticket requirements per repository. Check a file path to see the exact rule and source layer the reviewer will use.



Feedback and learning
GitHub reactions, replies, resolved threads, and Slack feedback provide quality signals. Peertic can propose guidelines for matching files; admins can review, edit, approve, or revert them.


Ticket-aware review
Bring linked requirements into a review through project management tools such as Jira and through GitHub issues. Compatible MCP servers can provide context from other project, documentation, or knowledge tools. Peertic can compare code with acceptance criteria and write the outcome back when configured.


Deployment and model choice
Self-host on your own machine or infrastructure, or request dedicated hosting on your preferred infrastructure. Select a model provider or private gateway and configure review defaults, optional MCP context, and telemetry.



Keep review decisions visible
Connect each repository to its ticket source and team channel. Peertic publishes line-level findings and merge checks in GitHub, then keeps Slack current with verdicts, severity, linked requirements, and links back to the PR.
Teams can catch unmet acceptance criteria before merge, distinguish blockers from follow-up work, and request another review after a fix. Feedback on individual findings informs quality metrics and proposed guidelines.



Sessions and administration
Browse and compare saved sessions, export reports, manage portal accounts, and inspect the event trail. This gives administrators a record of what ran and what it produced.





