Do I have to review on GitHub?

No. Any pull request link on a ticket opens a panel beside it with the summary, evidence, timeline, diff and checks, and you can comment, revise, close or merge from there. GitHub still works the same way if you prefer it.

What does the reviewer agent check?

Correctness, side effects, compatibility, performance, scope and whether the evidence supports the claim. It reads the command log from the sandbox rather than trusting the agent's summary, and asks for a revision only for concrete defects.

Can a pull request loop on revisions forever?

No. Reviewer, CI and changes-requested revisions share one automated cap per pull request, 1 by default and at most 5. Automated triggers also stop once a ticket has had 3 runs.

Will Starko merge without me?

Not unless you allowed it. Auto-merge is off by default. The onboarding widget pull request merges itself when checks pass, and onboarding offers auto-merge for the repositories you connect there. Branch protection always applies.

What am I billed for?

Merged pull requests, counted once each. A pull request closed without merging is not billed, and a merged fix that is later reverted is credited back.

Read the proof, ask for changes,and merge without leaving the ticket.

Every pull request Starko AI opens comes with the evidence of what it ran, a reviewer agent's verdict and your CI result. Send it back, or merge it from the panel beside the ticket. The merge closes the ticket, and it is the one thing Starko bills for.

starko-me/starko-v2#432

feat(whatsapp): add the ability to delete a WhatsApp template

starko-ai[bot]·updated 20 hours ago· Open

mainstarko/fix-d2728b0c-ad880f 9 files+1,354 -62

Run

Open ticket

Reviewer revisePR openCI: passingFeature · mediumprompt v14

Reproduction

Reproduced

Picker listed 41 stale templates; no delete affordance anywhere in the UI.

Verification

13 commands run in the sandbox

Agent’s claim: deletion removes the template on Meta and the local mirror row; the picker drops it from every send and broadcast flow.

npm run lint
✔ 0 problems
exit 0
npm run typecheck
tsc --noEmit · 0 errors
exit 0
npm test -- whatsapp-template
Tests: 8 passed, 8 total
exit 0
npm run test:e2e -- template-manager
3 passed · deleted a template in the seeded sandbox
exit 0

Reviewer agent

Risk: medium

Side effects: lowCompatibility: lowPerformance: lowVerdict: reviseAuto-revised

Merge pull request #432?

This will squash and merge into main as the STARKO GitHub App. The merge is recorded on the ticket with your name.

CancelConfirm merge

At a glance

Review and merge in short.

Where it opens: In a panel beside the ticket, from any pull request link. ⌘-click still goes to GitHub.
Reviewer agent: Rates overall risk plus side effects, compatibility and performance, and gives a verdict.
Automated revisions: 1 per pull request by default. Each project sets 0 to 5.
Who can merge: Owners and admins, from the panel, the sidebar, ⌘L or Slack.
Merge safety: The merge is pinned to the commit you last saw. New commits make GitHub refuse it.
After the merge: The ticket moves to closed and the merge is counted once.
Closed without merging: Not billed. The pull request becomes an eval case.
Reverted later: The run is marked reverted and credited back.

Evidence

Every Starko pull request arrives with its proof.

The panel's Evidence tab shows what the run did, not only what the agent says it did. The reproduction, the verification commands taken from the sandbox session with their exit codes, before and after screenshots, and the reviewer agent's ratings. The pull request body on GitHub carries the same evidence under Problem, Reproduction, Fix, Verification, Risk and Out of scope.

Reproduction reads Reproduced before fixing, Could not reproduce, or Reproduction not applicable for changes that are not bugs.
If no test, typecheck or build command was seen, the panel says to treat the fix as unverified.
When the project has a test command, Starko runs it itself in the sandbox after the agent finishes and records the real exit code.
The agent's handoff lists What you need to do (a migration, an env var, a setting), its own concerns and where it deviated from the ticket.
The Summary, Timeline and Files tabs show the description and checks, the PR's history, and the full diff in unified or split view.

Review stage

A reviewer agent and your CI read it before you do.

When the run opens its pull request, a second agent reviews it with the diff, the evidence, the agent's own concerns, the CI state and the ticket's classification. It trusts the command log over the agent's claim. It rates overall merge risk as low, medium or high, rates side effects, compatibility and performance, lists concerns and names missing evidence. The ticket's Starko AI tab shows the verdict next to the CI state.

The verdict is approve or revise. Revise is reserved for concrete defects it can name, never for style.
Small diffs, up to 40 changed lines, skip the model review unless they touch sensitive paths such as auth, billing, payments, permissions, migrations or webhooks.
A revise verdict shows as Revise requested on the ticket and sends the run back with the reviewer's instructions. Fix this on a single finding starts a run scoped to that finding.
Your team's own pull requests can be reviewed too: turn on Review pull requests when they open in the project's Starko AI settings, or mention @starko on any pull request. The review is one comment with Overview, Concerns and Verdict.

v2.starko.one/dashboard/tickets/4f2c…

Tickets/STK-432

72%

Add the ability to delete a WhatsApp template

In Progress MediumSVStefan Vukmanović Ana Kovač · Acme d.o.o.starko-me/starko-v2 Fix with Starko AI

Starko AI2 runs

Reviewer reviseFeature · mediumstarko-me/starko-v2 · 6 minutes ago · 4m 12s · 184,220 tok

Evidence

13 verification commands 2 screenshots

Fix

PR #432 · open

Permission-gated template manager with confirmation and server-side deletion on Meta and the local mirror row.

Review

medium riskRevise requestedCI: passing1 concern

Picker: a deleted template could stay selected in an open composer. Invalidate the picker query after deletion.

Automated follow-ups: on · next run: Feature · medium

OperatorFeature · mediumPR openrun 1 · 1 h ago · 3m 48s · 121,906 tok

Opened PR #432 with evidence. The reviewer agent asked for a picker-query invalidation, so run 2 is revising.

Revisions

Revisions go back to the same run, within a cap you set.

Three things send a pull request back automatically: the reviewer agent's revise verdict, a red check suite (the failing output goes with it), and a GitHub review that requests changes. Each resumes Starko AI on the same branch, so its pushes update the same pull request. Together they share one cap per pull request: 1 by default, set from 0 to 5 per project.

GitHub reviews and line comments on a Starko pull request are mirrored into the ticket, marked via GitHub, so the next run reads them.
Only the repository's owners, members and collaborators count. Reviews from outside contributors and bots are ignored.
Mentioning @starko in a GitHub review or comment resumes the run by hand. It does not use up the automated cap.
A red result for an older commit is ignored; only the pull request's current head can trigger a revise.
From the panel's menu, Ask Starko AI to revise drops you into the ticket with a mention ready. On a conflict the merge button becomes Ask Starko AI to resolve conflicts.
Turn off Automated follow-ups on the ticket and Starko AI stops after the current run.

GHjonas-kleinvia GitHubNov 2 at 14:05

Changes requested

The export now includes the last row, but the header row is written twice when the list is empty. Cover the empty case too.

GitHub reviewBug · smallnorthwind/web · just now

Fix

Starko AI is preparing a fix…

PR #219 · opensame branch, same pull request

Review

low risk ·automated follow-ups used (1/1)

Automated follow-ups: on

Merge

Merge from Starko, and the ticket closes itself.

The panel's main button follows the pull request's state: Ready for review on a draft, then Squash and merge, Merge or Rebase and merge, as your repository allows, with a confirmation. The merge is made as the STARKO GitHub App and recorded on the ticket with your name. When GitHub reports the merge, the ticket moves to its closed status, and a ticket a person already closed or cancelled keeps that status.

The merge request carries the commit the panel last showed you. If new commits landed in the meantime, GitHub refuses rather than ship code you have not seen.
Right-click a session in the sidebar for Merge pull request, with the same confirmation.
From ⌘L or Slack, Starko merges only when you explicitly say to. It refuses on failing checks, conflicts, branch protection or a closed pull request; pending checks or a revise verdict need you to say merge anyway.
Merging from GitHub works the same way: the webhook closes the ticket and counts the merge.
Merging needs an owner or admin. Reading check results needs the GitHub App's Checks: read permission, and the panel tells you when it is missing.

Open ticket

Open on GitHub#219

Merge pull request

Close ticket

Archive ticket

Delete ticket

Merge pull request #219?

The pull request for "Export CSV drops the last row" is merged on GitHub with the repository's default method.

CancelMerge pull request

Auto-merge

A bot merges only where you said it could.

Auto-merge is set per project. Two things turn it on: the onboarding pull request that installs the Starko widget merges itself once its checks pass, and the onboarding setup has Merge Starko's PRs when checks pass for the repositories you connect there. That switch starts on, so turn it off during setup if you want to merge every fix yourself. Branch protection still applies.

The reviewer agent must have finished without asking for a revise.
Checks must be green. If the GitHub App cannot read checks, Starko does not merge.
No conflicts, no branch protection block, no draft. A draft is marked ready first.
The merge is pinned to the commit the checks ran on, and an internal comment on the ticket records it.

Outcomes

What a merge costs, and what a closed pull request teaches.

A merged pull request is counted once, whether it was merged in Starko or on GitHub. That is the event Starko bills; feedback, answers, triage and recommendations are free (see pricing). A pull request closed without merging costs nothing and becomes an eval case. A merged fix that a later push reverts on the default branch is marked reverted and credited back.

Eval cases record the prompt version that produced them, so a prompt change can be replayed against past failures before it ships.
Reverts are detected from GitHub's revert pull requests and from git revert commits that name the merge.
Settings, Starko AI is the ledger: merged PRs, merge rate, time to merge and cost per merged PR, with every run's trigger, outcome, risk and CI state.
See the whole loop, from a stuck visitor to this merge, on How it works.

v2.starko.one/dashboard/settings/starko-ai

Settings/Starko AI

72%

Starko AI

Every fix run, what came of it, and what it cost: the ledger behind the @starko agent.

Merged PRs

Merge rate

85%

merged ÷ runs that opened a PR

Time to merge

3h 40m

median, run start → merge

Billed / merged PR

$18.20

platform cost $6.90