For teams shipping more pull requests than anyone can read
More code, please.
CodeGhoul is a code review agent for GitHub. Maeve reads every changed line of every pull request, on every push, and leaves a review you can act on: inline comments, a summary, and a check run you can require before merging.
She's in private pilot before launch. Write to contact@codeghoul.ai.
Pick a book to see what she leaves
[✓] Read diff...
She reads past the diff.
The diff is where she starts. Before she writes a word, she also reads:
- The base revision, so each finding names what the change altered.
- Callers of everything the change defines or removes, from an index of the repository.
- Every other open pull request, for shared migration numbers, version bumps and the same issue fixed twice.
- Linked issues from GitHub, Jira or Linear, with each acceptance criterion marked met, not met or not verifiable.
- Scanner evidence on the changed files: secrets, dependency advisories and pattern rules.
A changed path she couldn't read, because it's binary, too large or past the cost limit, is named in the summary, and the check goes neutral.
- readbase revision a81c0d2ok
- readchanged lines2 of 2
- tracecallers of users.find()3 files
- compareother open pull requests4, no collision
- judgeissue #301 · AC-1, AC-2both met
- scansecrets · advisories · rulesclean
[✓] Look for risks...
A second read where it matters.
Second review. A large change, or one touching paths you name, gets a second review on another model. It reaches its own verdict without seeing the first one's.
Security pass. Add the review:security label, comment @codeghoul security with write access, or let path rules ask for it. By default they cover auth and permission code, CI workflows, hooks, agent tool configs and dependency manifests. The pass weighs the scanner evidence and posts its own check run, agentic-security-review, with one verdict: Pass, Block or Incomplete.
security_path_rules: - "**/auth/**" - ".github/workflows/**" second_review: mode: conditional # off | conditional | always min_changed_lines: 500 paths: ["migrations/**"] rung: mode
[✓] Suggest fixes...
Fixes you can commit. Prompts your agents can use.
When a fix is certain and fits inside the change, it comes as a GitHub suggestion, checked to apply cleanly to the head before she posts it. You commit it in one click.
Every inline comment also ends with a fix prompt: the path, the line, what was expected, what happens now, and how to check the fix. Paste it into your coding agent.
MaeveEDGE CASEShighdemo finding
A product with no ratings passes [], and reduce without an initial value throws on an empty array.
- const total = scores.reduce((a, b) => a + b)+ if (scores.length === 0) return null+ const total = scores.reduce((a, b) => a + b, 0)
Fix prompt
- repository
- example/shop
- head_sha
- c47d1a9
- path
- src/products/rating.ts
- line
- 13
- expected
- a product with no ratings gets null
- actual
- reduce throws a TypeError on []
- how_to_verify_fixed
- averageRating([]) returns null
[✓] Leave comments...
Quiet on purpose.
- A cap on inline comments, most severe first. The rest go in the summary, grouped by file.
- Floors for certainty and severity, per path if you like, so guesses and docs nits stay out of the diff.
- Generated, vendored and minified files, binaries and lockfiles are left out, and listed.
- Dismissals stick. Reply
@codeghoul dismiss: <reason>. A dismissal from a maintainer who didn't write the pull request, or from two collaborators, becomes a suppression she follows on later reviews of that file. Every summary lists it until it expires. - Policy comes from the base branch, so a pull request can't loosen its own review.
certainty_floor: likely # possible | likely | certain severity_floor: medium inline_cap: 10 noise: severity_floors: {"docs/**": high} skip_classes: [generated, vendored, lockfile, binary, minified]
- S3"Unused export" in src/legacy/report.tshid 2
[✓] Repeat...
Every push. Built for teams with coding agents.
She reviews each new head and keeps one thread per finding. It gets Still present while the problem stays, reopens if it comes back, and closes as Resolved when it's gone.
- A pull request costs at most 12 credits a month on the default tier, however many times your agents push it.
- Bot accounts never take a seat.
- Parallel agents collide. She compares every open pull request for shared migrations, version bumps and duplicate fixes.
- Agents can ask first. Review a branch from the command line before it becomes a pull request, or connect her as an MCP server with
review_diff,get_findingsandexplain_finding.
- 3f9c2e1Empty cart divides by zero.high
- 5b0e771Still present.
- 8a41d07Resolved in 8a41d07.closed
- agent/refund-receipts9 pushes12.0 capped
- agent/rating-rounding2 pushes6.0
- agent/webhook-retries1 push4.5
- seats taken by bot accounts0
Your call
The gate is yours.
Out of the box her check run reports and never blocks. Add a gate to the config, and a finding at your severity, and at or above your certainty floor, fails deep-code-review. Require that check in branch protection and the failure stops the merge.
When she's wrong, a maintainer comments @codeghoul override: <reason>. That head passes as neutral, and the check run records who let it through and why. The next push is judged again.
Her reviews never approve on their own. Turn on auto-approve and she approves only small, low-risk changes she read in full, with no findings and no security paths, and withdraws the approval if a later push doesn't qualify.
gate: fail_on: high # high | medium | low | never incomplete: neutral # neutral | failure
- [x]deep-code-reviewrequired
- [ ]agentic-security-reviewonly if every pull request gets a security passoptional
@codeghoul override: fixture is flaky upstream, tracked in #412
deep-code-review → neutral for 8a41d07, recorded with who and why
Access
What she can touch.
She works as a GitHub App. Her reviews, comments and check runs come from her bot account, never from a person's.
- Each customer's reviews run in a worker of their own, with its own storage.
- The service that routes GitHub's events keeps which installation goes to which worker, and nothing else. Pull request content passes through it without being written down or logged.
- Access tokens are issued for each job and never written down.
- Nothing that contains a detected secret is posted to your pull request.
| Permission | Access | What for |
|---|---|---|
| Pull requests | write | read the diff, post the review and its comments, and approve if you turn on auto-approve |
| Checks | write | complete her check runs, record overrides |
| Contents | read | fetch the base and head, read .codeghoul/ |
| Actions | read | read a head's scan results for the security pass |
| Issues | read | receive the comments that carry commands |
| Metadata | read | look up repositories and roles |
Questions
Does she replace human review?
No. She reads every changed line first and leaves the decision with your team. Her reviews never approve on their own.
What happens when she's wrong?
Reply @codeghoul dismiss: <reason> to her comment. A maintainer's dismissal, or two collaborators', stops that finding on later reviews of that file. To let one push through the gate, a maintainer comments @codeghoul override: <reason>.
Which languages does she read?
Any language in the diff. Tracing callers goes deepest in Python, JavaScript, TypeScript, Ruby, Rust and C#; for other files the summary says where the trace stopped.
Does it work with GitLab?
GitHub comes first, as a GitHub App. Ask us about GitLab.
Who makes it?
Manufactoria s.r.o., in the Czech Republic. Maeve is also the Reviewer on Manufactoria's delivery team.
Want her on your repositories?
We're running a small number of pilots before launch.
Discuss a pilot