Pull request reviews
Enable Pro and Team PR reviews, choose focus areas and comment style, and apply generated fixes.
Availability
PR reviews run on the Pro and Team plans. Both include the prReviews entitlement.
The review runs when a pull request is opened, reopened, synchronized or marked ready for review. Draft pull requests are skipped, and so are pull requests opened by a bot.
Enable
Turn on pull request analysis for a repository from its settings, or configure it from the terminal:
dxnx analyze config-set owner/repoconfig-set asks for the review toggle, comment style, ciSkip and the token budget, then saves
them for the repository.
Focus areas
Pick one or more focus areas. Findings outside the selected areas are filtered out before comments are posted.
| Focus area | What it covers |
|---|---|
ARCHITECTURE | Module boundaries, coupling and structural patterns |
PERFORMANCE | Hot paths and changes that affect runtime cost |
SECURITY | Security invariants, dangerous sinks and exposed secrets |
STYLE | Conventions and readability |
Comment style
| Style | Behaviour |
|---|---|
DETAILED | Full review with severity, code snippet and a suggested fix |
CONCISE | Only the finding type, severity, score and message |
OFF | Run the analysis without posting review comments |
Token budget
Each pull request run has a token budget between 10,000 and 100,000. The default is 30,000. Values outside the range are clamped, so a large diff cannot consume an unbounded amount of context.
Skip a run
When ciSkip is enabled in the repository settings or with dxnx analyze config-set owner/repo, a
commit message containing [skip ci] skips PR analysis for that update.
chore: regenerate fixtures [skip ci]What is analyzed
Only the diff is analyzed, never the whole repository:
- changed files are collected from the pull request;
- files matching the exclusion patterns are dropped before analysis;
- the remaining changes go through Sentinel and Mapper;
- impact analysis maps the changed files to the graph nodes and interfaces they touch.
The exclusion list starts with Doxynix's own rules — ignore files, generated directories such as
dist, build, vendor and node_modules, and asset files such as stylesheets, images and fonts.
Custom patterns can be added on top. Individual changed files with more than 1,000 changed lines
(additions + deletions) are dropped too, so a single huge file cannot crowd out the rest of the
change.
Findings
Findings are posted as one batched pull request review with inline comments, rather than as a stream of separate comments. Every finding carries a stable signature derived from its file, line, type and title. On a later run, a finding with the same signature is recognized, so the same issue is not posted twice, and existing review comments are left unchanged.
Fixes
Generated fixes are available for the findings posted by a review:
dxnx pr fixes
dxnx pr fix <id>
dxnx pr fix-apply <id>dxnx pr fixes lists the fixes available for a repository, dxnx pr fix <id> shows the patches
without changing anything, and dxnx pr fix-apply <id> opens a pull request with the fix applied.
The same fixes are available from the dashboard.