AI review for teams with business rulesAI code review for teams with real business rules

Your AI reviewer knows your business.

Precept reads every pull request against the rules your company runs on. Logic bugs get caught in review, not in production.

Create free account See pricing

Free for up to 3 developers · No credit card · GitHub and Gitea

Drag to spin · press a key

helix/orders-serviceRefactor order cancellation to support partial refunds#482

Blocking · 1 critical

src/orders/cancelOrder.ts

42- if (order.status !== 'PENDING' && order.status !== 'PAID') {

43+ if (order.status === 'SHIPPED' || order.status === 'DELIVERED') {

44+ throw new BusinessRuleError('ORDER_NOT_CANCELLABLE');

CriticalInvoiced orders can now be cancelled96%

The new check only blocks shipped and delivered orders, so invoiced orders reach the refund call.

BR-014Invoiced orders are immutable

Which statuses can be cancelled

Your rule

PENDINGPAIDINVOICEDSHIPPEDDELIVERED

This pull request

PENDINGPAIDINVOICEDSHIPPEDDELIVERED

The invoice stays valid while stock is released and the customer is refunded. Finance would see an invoice for a cancelled order.

1 critical2 high3 medium1 low

The gap in code review

Code review that understands more than code.

Generic tools check syntax and style. Your incidents come from broken business rules that only your team knows.

A generic AI reviewerApproved

Nit: consider extracting the status list into a constant.

Suggestion: add a doc comment to cancelOrder().

Looks good overall. The logic is clear and tests pass.

Invoiced orders can be cancelled after merge.

PreceptBlocking

Invoiced orders can now be cancelled.This violates BR-014 Invoiced orders are immutable. Suggested fix attached.

Refund call has no idempotency key (ARCH-007).

Customer email is logged (SEC-003).

The bug is caught before it ships.

Features

Review that follows your rules.

Catch business logic bugs before they reach production, without changing how your team works.

Every pull request, reviewed in minutes

Developers open pull requests as usual. Precept reads each one against your rules and standards.

A review you can verify

Each finding cites the rule it breaks, with evidence, a confidence level and a suggested fix.

Fits your Git workflow

GitHub and Gitea, cloud or self-hosted. Rules sync from the Markdown already in your repositories. Ask about findings from Claude Code or Cursor through MCP.

See what gets fixed before merge

Track findings by severity and repository, and how many your team resolves before code ships.

How it works

From connected repository to first review in one afternoon.

Connect your repositories

Install the GitHub app or point Precept at your Gitea instance. Pick the repositories to review.

Teach it how your business works

Import the Markdown you already have, or write rules in plain language. Scope them to repositories and paths.

Get a review on every pull request

Findings appear inline within minutes, each with the rule it cites, a confidence level and a suggested fix.

Project Knowledge

Write the rule once. Precept applies it to every pull request.

Business rules, architecture decisions and standards, kept like folders your team already understands. Open one to see what Precept reads.

BR-011 Discounts and gift cardsHIGH

BR-009 Refund capCRITICAL

BR-014 Invoiced ordersCRITICAL

Business rules24 rules

ADR-003 Event-driven ordersADR

ARCH-002 Thin controllersRULE

ARCH-007 Idempotent callsHIGH

Architecture9 decisions

STD-004 NamingINFO

SEC-003 No PII in logsMEDIUM

STD-021 No per-item queriesMEDIUM

Coding standards12 standards

Hover to lean · click to open

Beyond the pull request

Your rules, wherever your team asks.

The same reviews and knowledge reach your editor through MCP, and your clients through docs generated from the code.

Included in every plan

Ask about your findings from Claude Code or Cursor

Precept is an MCP server. Connect your AI coding tool once and ask what is blocking a pull request, why a rule applies, or whether your last push fixed it. Read only by default, with your own permissions.

~/orders-service

› What’s blocking my PR #482?

⎿ precept · get_review(pr: 482)

One critical finding: invoiced orders can now be cancelled, which breaks BR-014. Precept suggests keeping an allow-list of PENDING and PAID.

Claude CodeCursorVS CodeAny MCP client

Add-on

Docs your clients can read and ask about

Generate documentation from a repository, keep it private or share it with client accounts. When a client has a question, they ask the docs and get an answer with its sources, not a ticket.

HCorders-service docsShared with Acme Retail

Can an invoiced order be cancelled?

No. Once an invoice exists the order is reversed with a credit note.

SourcesOrder lifecycleRefunds and credit notes

Private by defaultClient accountsPublic linkInternal pages

Simple pricing

Per developer. Start free and upgrade when your team does. Bring your own Gemini, OpenAI or Anthropic key.

Starter

FreeUp to 3 developers

For trying it on real code

5 repositories

50 reviews per month

10 knowledge documents

GitHub and Gitea

Community support

Get started

TeamMost popular

Per developer / month

Great for product teams

Unlimited repositories

Unlimited reviews

Unlimited knowledge

Merge protection status

Email support

Get started

Business

Per developer / month

Great for several teams

Everything in Team

Review policies per team

Audit log, 12 months

Single sign-on (SAML)

Priority support

Get started

Enterprise

CustomAnnual contract

For regulated organizations

Everything in Business

Custom data retention

Custom contract and invoicing

Dedicated success manager

Security review support

Compare all plans →

Add-onDocs

Documentation generated from your repositories. Share it with client accounts and let them ask questions with AI. Priced separately, with a Docs price for each plan.

Team + [PRICE] / monthBusiness + [PRICE] / monthEnterprise customSee how Docs works

FAQ

Questions teams ask first.

How is this different from other AI code reviewers?

Most reviewers look at the code in isolation. Precept also reads your business rules, architecture decisions and standards, and cites the exact rule behind each finding, so you can verify it in seconds.

Do we have to write a lot of rules before it is useful?

No. The first reviews work without any rules. Add rules as you find them, or import the Markdown documents already in your repositories.

Can it block a merge?

Yes, if you want it to. Precept sets a commit status you can require in branch protection. You choose the severity that blocks, per repository.

Does it work with self-hosted Gitea?

Yes. Connect your instance with an access token and a webhook. Reviews are posted as pull request comments.

Can I use Precept from Claude Code or Cursor?

Yes. Precept is an MCP server. Each person connects their own tool and gets their own permissions. It is read only unless your organization allows changes such as re-running a review.

Who can read the generated docs?

Only your team, until you share them. You can invite client accounts, who see nothing else in Precept, or create a public link. Pages marked internal stay hidden from clients and from their AI answers.

Which AI does Precept use?

Yours. Connect your own API key from Google Gemini, OpenAI or Anthropic. You pay the provider directly, and you can switch at any time. No key yet? Gemini has a free tier.

What happens to our code?

For each review, Precept sends the diff, nearby code and the relevant rules to the AI provider you chose, using your key. Data handling then follows that provider’s terms. [Confirm Precept’s own retention terms before launch.]

How do we know a finding is right?

Every finding shows its rule, the evidence behind it and a confidence level. Mark a finding as not a violation and Precept records it, so the team can refine the rule.

Stop finding business logic bugs in production.

Connect a repository, add your first rule and review a real pull request today.