Your team’s rules, checked on every PR.
Write the rules your senior engineers repeat in every review, in plain English. Megicoder checks every pull request against them and points to the exact line that breaks one.
Never log personal data such as emails, phone numbers or card numbers.
scope: **/*severity: HighAll API handlers need input validation before touching the database.
scope: api/**severity: HighNo console.log in application code. Use the shared logger.
scope: src/**severity: Lowhit: checkout/discount.ts:61Database access goes through the repository layer, not raw queries in services.
scope: services/**severity: MediumRules that read like review comments
No query language or plugin to write. A rule is a sentence, a scope and a severity, stored in your repository next to the code it governs.
Starter rule packs
Begin with packs for API safety, logging hygiene, React, Django or Spring, then edit freely.
Compliance-minded rules
Encode data-handling rules like masking personal data so they are checked, not just documented.
Exact-line findings
Every hit links to the line and quotes the rule it breaks.
Test rules on a branch
Try a new rule against recent PRs before turning it on for everyone.
Explains itself
Each finding says why the code breaks the rule and how to fix it.
Admin-only org rules
Organization rules can be locked so only admins can change or disable them.
Common questions
Precise enough for most review conventions. For each rule you can preview hits on recent PRs and tighten the wording before enabling it.
Yes. Mark it as required and Megicoder reports a failing status check on your git platform until it is fixed or overridden by a reviewer.
Free includes the standard rule set. Custom Team Rules are part of the Team and Enterprise plans.
git merge feat/first-review into main
Review your
first repo free.
One repository, AI review on every pull request, no time limit. Connect it in about five minutes and the next PR gets a first pass in under a minute.