Inline on the hunk
Each comment sits on the line it marks. Citations are paths and line numbers your editor can open.
Product
A reader that already knows the tree.
GitHub and GitLab. Inline comments. Severity you can tune: quiet, standard, strict. Ignore paths. Custom guidelines as markdown the reviewer must obey.
GitHub
GitLab
st.
Severity tuner
How loud the margin should be on this org.
Standard comments on pattern drift, missing callers, and risky diffs. House guidelines apply.
01
Pull request review
The agent reads the diff, retrieves neighbors, and writes comments a human can accept or dismiss. Dismissals can train the next pass if you opt in.
Accept or dismiss
Accepted comments stay in the thread. Dismissed ones can update org memory when learning is on.
Agent-authored diffs
A second reader, separate from the patch author. Useful when a coding agent opened the PR.
02
Codebase index
Private index per org. Incremental updates on push. Monorepo-aware. Pair with a dedicated secrets scanner for credentials. Stetrel reviews code shape. A scanner still hunts keys.
Graph + embeddings
Files, functions, and callers are nodes. Retrieval pulls the neighbors a one-file read would miss.
Refresh on merge
Default-branch pushes rebuild the changed slice. Large monorepos index by package boundary.
Ignore paths
Vendor trees, generated protobufs, and lockfiles can sit outside the comment budget.
03
Team standards
Write standards in plain English. Point Stetrel at repo-specific context. Optional: read your team’s review comments to pick up house voice.
# .stetrel/guidelines.md
Auth tokens stay scoped to the tenant in apps/api/tenants.py.
Do not mint admin scopes from session helpers.
After deleting a public function, search callers in billing/ and apps/.
Log extra fields must match observability/logfmt.py.
New HTTP handlers need a test in the nearest tests/ folder.
04
Private install
Same binary, your cloud. For teams that keep source inside a perimeter. Air-gapped packs ship with pinned weights and an offline index worker.
Where the desk earns its keep
High-velocity product orgs
Every PR, including the small ones. The index already knows last week’s helper.
Regulated code
VPC path. Source, embeddings, and comments stay in the account legal already named.
Agent-written patches
A second reader with the tree in memory. Humans still merge.
Onboarding
New hires see comments that point at house patterns.
Teams
For engineering orgs where review is the bottleneck. If you merge a lot, you are the customer. We name roles here until legal clears logos.
Staff engineer
Wants comments that cite the helper three files away, then a human pass on design.
Engineering manager
Wants fewer rubber-stamp reviews and a record of what the team already decided.
Security lead
Wants least-privilege Git access, a VPC option, and a written deletion path on uninstall.