Zapat

Getting Started

Trigger your first job

Label a GitHub issue or comment @zapat and watch your first AI-generated PR appear.

Updated March 3, 2026

Once your repository is connected, triggering a job is as simple as adding a label to a GitHub issue or commenting @zapat. Zapat receives the webhook within seconds and begins working.

Issue label triggers

These labels, applied to a GitHub issue, start specific workflows:

  • "zapat:triage" — Zapat reads the issue and produces a triage report with complexity estimate and implementation plan.
  • "zapat:implement" — Zapat triages and then implements the issue, opening a pull request.
  • "zapat:research" — Zapat researches the topic and posts a summary as a comment.
  • "zapat:write-tests" — Zapat writes tests for the code related to the issue.

PR label triggers

These labels, applied to a pull request, trigger review and fix workflows:

  • "zapat-review" or "agent" — Zapat reviews the PR and leaves comments.
  • "zapat-testing" — Zapat runs tests against the PR.
  • "zapat-rework" — Zapat implements the requested changes from a review.
  • "zapat-ci-fix" — Zapat reads the CI failure and applies a fix.
  • "zapat-visual" — Zapat performs a visual verification of the changes.

Triggering via @zapat mention

You can also trigger Zapat by mentioning "@zapat" or "@zapat-ai" in an issue or PR comment. If the issue has already been triaged and you write something like "@zapat go ahead and implement this", Zapat will dispatch an implement job. On a PR, a mention triggers a review.

Tip

Zapat adds an 👀 reaction to your issue or comment to confirm it received the trigger. If you do not see the reaction within 10 seconds, check your GitHub App installation.

Auto-chaining: triage to implement

When you use "zapat:triage", Zapat analyses the issue and posts a triage summary comment. If the triage agent determines the issue is straightforward enough to implement immediately, it automatically chains into an implement job without you needing to add another label. You will see two sequential jobs in the dashboard: one triage job, then one implement job that opens the PR.

Monitoring progress

  • Go to Pipeline in the Zapat dashboard to see your job in real time.
  • Jobs move through states: pending → queued → running → completed.
  • Zapat posts a live-updating comment directly on your GitHub issue as it works — updated approximately every 2 minutes. You can monitor progress without opening the dashboard.
  • When the job completes, the PR link appears in the dashboard and on the GitHub issue.
Connect your first repositoryDashboard overview

Was this article helpful?