> ## Documentation Index
> Fetch the complete documentation index at: https://docs.niteshift.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub

> Trigger and observe Niteshift tasks from pull requests, with check runs and PR comments wired to your repository.

GitHub is Niteshift's primary surface. The Niteshift GitHub App grants repository access and lets
you trigger tasks from PR comments, with results posted back as check runs and comments on the PR.

## Setup

<Steps>
  <Step title="Install the GitHub App">
    From the setup page (or [niteshift.dev](https://niteshift.dev) on first sign-in), install the Niteshift GitHub App on your account or organization.
  </Step>

  <Step title="Choose repositories">
    Pick **All repositories** or select specific ones. Niteshift only sees repositories you grant.
  </Step>

  <Step title="Re-manage access later">
    Open your GitHub organization settings to add or remove repositories at any time. The Niteshift dashboard reflects the new list immediately.
  </Step>
</Steps>

## How to use

Comment `/niteshift` on any pull request you authored to start a task scoped to that PR. Only the PR
author can trigger `/niteshift` commands.

```
/niteshift fix the failing tests
```

Niteshift checks out the PR branch and uses it for any commits the agent pushes; tasks don't open a
new branch. The prompt includes the PR title, body, and diff, and [autofix](/autofix) activates
automatically so the agent addresses CI failures and review comments as part of its work.

A bare `/niteshift` with no prompt runs autofix against the PR's current state.

If a task is already running on the PR, a second `/niteshift` routes to the same task: your prompt
becomes a follow-up message, or a bare `/niteshift` re-triggers autofix.

<Note>
  See [Autofix](/autofix) for how Niteshift iterates on CI failures and review comments
  automatically.
</Note>

## What you receive

The trigger comment gets reactions as the task progresses:

* 👀: command detected
* 🚀: task started
* 👎: failed to start

Niteshift then posts:

* A reply comment with a link to the task workspace
* A check run named **Niteshift Fixes** with results
* Commits pushed back to the PR branch when the agent finishes

Niteshift uses a stop hook that asks the agent to commit changes when it finishes. PRs respect your
repository's PR preference (defaults to draft). If you want code review bots like CodeRabbit, Cursor
Bugbot, Codex Review, or Claude Code Review to fire on every push so [autofix](/autofix) can iterate
on their feedback, switch the preference to **ready**. Most of these bots skip drafts.

You can opt into auto-archiving the task when the PR closes from your user preferences. It's off by
default.