When it activates
Autofix runs when:- CI on your PR finishes with at least one failed check. Autofix waits for the full run to complete before acting.
- A review comment is posted from a source Autofix is set to address. Bot comments are on by default; your own comments and other reviewers’ comments are off by default (see which comments it addresses).
- You (the PR author) post
/niteshifton the PR. This kicks off Autofix on the task tracking the PR, or creates a new task with Autofix enabled if none is tracking it yet. Append a prompt to steer the run, e.g./niteshift focus on the failing snapshot tests.
While Autofix is working, a Niteshift Fixes check run appears on the PR and links to the task.
Which comments it addresses
Autofix decides whether to engage a review comment based on who left it. Each source has its own default, set under Settings → Preferences:- Bot comments: on by default. Actionable feedback (CodeRabbit, Cursor Bugbot, Codex Review, Claude Code Review) gets fixed; noise is ignored.
- Your own comments: off by default. Turn this on to have Autofix act on comments you leave on your own PR.
- Other reviewers’ comments: off by default. Turn this on to have Autofix act on comments from teammates reviewing the PR.
autofix.ignoreChecks to exclude specific CI
checks.
Where to turn it on
Autofix can be turned on at three levels:- Repository: under Settings → Preferences. Applies to every PR you create with Niteshift in that repository.
- Per integration: separate toggles for tasks created from Linear or Slack, in Settings → Integrations.
- Per task: override the default for a single task, on the task page.
Mentioning @niteshiftdev
Mention@niteshiftdev in a comment on the PR, including an inline comment on a line of the diff,
to have Niteshift address it, regardless of your comment-source settings. Text after the mention is
passed to Niteshift as a prompt, e.g. @niteshiftdev rewrite this using the existing helper.
Only the PR author can mention @niteshiftdev.