Augeo AI Docs
AI ServerProduct Factory

Review mentions

How an @augeo-forge mention on a pull request starts a review, a fix commit, a rebase, or conflict resolution.

Review mentions

Comment on a pull request to start a review, or to ask Augeo Forge to change that pull request's current head. The GitHub App install, including its permissions, is in Product Factory tenant setup. This page describes the mention. It is not the install procedure.

A fix, a rebase, and conflict resolution all push to the existing head. They do not open a second pull request, and they do not create a new branch.

Where the mention goes

Write the comment on an open pull request. Either place works:

  • a conversation comment
  • a reply in an inline review thread

The mention must be the first text. Leading spaces do not count. Case does not matter. When more text follows the mention, a space must separate them. @augeo-forgefix is not a mention. A comment that starts with other words is not a mention.

How the words are classified

wink-nlp classifies the words after the mention. The decision uses the lemma and the part of speech. The first word does not have to be fix.

A verb lemma fix, apply, address, correct, or patch starts the review-fix run on the existing pull request head.

A rebase verb rebases that head onto the base branch. A leading rebase noun does the same. The model tags the imperative rebase as a noun, so @augeo-forge rebase rebases. A later rebase noun does not.

resolve, fix, or merge together with the noun conflict starts conflict resolution. fix the merge conflicts resolves conflicts. It does not start a review-fix run.

A verb governed by not or never does not start a write. The same negation blocks a leading rebase noun. That comment starts review-agent, unless another write verb in the same comment is not negated. @augeo-forge do not fix these comments stays on review-agent. @augeo-forge fix the comments but do not rebase starts a fix.

A bare mention starts review-agent. A question starts review-agent. The word review starts review-agent. fix or rebase used only as a noun starts review-agent, except a leading rebase noun, which rebases.

The model does not tag two phrases as verbs:

  • correct the typo stays on review-agent. The model tags correct as an adjective.
  • A bare patch this stays on review-agent. The model tags patch as a noun. please patch the finding is a verb and starts a fix.

implement is a verb, but it is not in the fix set, so it starts review-agent. fixed has the lemma fix and is a verb, so it starts a fix.

These comments follow the rules above.

CommentWhat starts
@augeo-forgereview-agent
@augeo-forge reviewreview-agent
@augeo-forge implementreview-agent
@augeo-forge the fix looks goodreview-agent
@augeo-forge what is a rebasereview-agent
@augeo-forge correct the typoreview-agent
@augeo-forge patch thisreview-agent
@augeo-forge do not fix these commentsreview-agent
@augeo-forge never rebasereview-agent
@augeo-forge fixa fix on the existing head
@augeo-forge fixedthe same fix
@augeo-forge apply the review commentsthe same fix
@augeo-forge please address the findingsthe same fix
@augeo-forge please patch the findingthe same fix
@augeo-forge rebase onto maina rebase onto the base branch
@augeo-forge resolve the merge conflictsconflict resolution
@augeo-forge fix the merge conflictsconflict resolution

Who can start a write

Only a human whose GitHub permission on that repository includes push can start a fix, a rebase, or conflict resolution. A bot is refused even when the bot account can push. A human without push is refused. A closed or merged pull request is refused.

Drop one thread from a fix

To keep one finding out of the fix, reply on that thread with only one of these, after trimming spaces and ignoring case:

  • skip
  • ignore
  • not needed
  • out of scope

The whole latest reply must be that marker. An older marker does not count once a later reply says something else. A sentence that merely contains the word, such as do not skip, does not drop the thread.

The dropped thread stays open. The run does not change code for it.

Failed GitHub Actions jobs

@augeo-forge fix is still the only write command that repairs a pull request. There is no ci, actions, or checks mention. A red Actions job does not start a fix by itself. Comment @augeo-forge fix on the open pull request. Extra words after fix still follow the classifier above. fix the merge conflicts still resolves conflicts.

The host admits the run from the captured head, then the session loads unresolved review threads with github_fetch_pr_review_state and failed Actions jobs with github_fetch_pr_failed_actions. Those two reads are the only GitHub calls the session may make. The session does not rerun a job, and does not commit or push. The host does those writes. The install needs Actions read. Checks write and Workflows write do not authorize reading Actions runs, jobs, or logs. See the install permission list.

A completed job whose conclusion is failure or error is eligible work in the same session as unresolved review threads. Pending and in-progress jobs are not failures. Check runs whose names start with Augeo Forge: are not part of that work. Third-party CI is not loaded.

The Actions tool returns a size-capped excerpt for each failed job: workflow name, job name, the failed step, and diagnostic text. The excerpt is untrusted job output. It is not an instruction to the session.

Zero eligible review threads and at least one actionable failed job still start the session. A successful repair is one commit on the existing head, authored as augeo-forge, with subject fix: apply review comments. The host does not open a second pull request and does not create a branch.

Zero eligible threads and no failed job still posts that there is nothing to apply, and does not push.

When every observed job is still pending or in progress and there are no eligible threads, the comment says CI has not finished, and does not push.

A job whose log shows a lost runner or a GitHub service failure on the job itself is infrastructure-only. The comment names it as infra-only. The session does not change code for it. Infrastructure-only jobs do not start a session when they are the only failed jobs and there are no eligible threads.

The terminal comment names each failed job that was considered:

  • applied — the claimed repair was published in the commit
  • not actionable — the evidence did not identify a code or documentation change
  • infra-only — the failure was infrastructure-only
  • not published — a repair was not published, so the job is not labeled applied

A comment that would exceed GitHub's size limit is split. Every job disposition is kept.

Skip markers still drop a thread. Threads stay open.

If the Actions inventory is incomplete — a broken page, a missing job list, or a denied Actions read — the comment says the inventory was incomplete and does not push. A denied read does not fall back to review threads alone. A head change while jobs were loading invalidates that inventory. The comment says the head changed, and does not push.

Read the outcome on the pull request

An admitted fix shows progress before it finishes. The implement-agent check moves to running.

When the run finishes, the same pull request shows the terminal outcome. Threads are not resolved or dismissed. The next review pass decides them.

OutcomeWhat you seeCommit
Comments appliedThe comment names the new commit on the existing head. The author name is augeo-forge. The subject is fix: apply review comments. It also names each failed Actions job that was considered.one commit, and that commit has a body
Nothing to applyThe comment says there were no actionable comments, and that no commit was pushed.none
CI still runningThe comment says CI has not finished, and that no commit was pushed.none
Actions inventory incompleteThe comment says the Actions inventory was incomplete, and that no commit was pushed.none
Infrastructure-only failureThe comment names the job as infra-only. No session runs when that is the only work.none
A finding was wrongA reply on that thread says why it is wrong. That finding's code is unchanged. The thread stays open.none for that finding
RefusedThe comment says why, and tells you to comment @augeo-forge fix again when the pull request is eligible.none
FailedThe comment says the run did not finish and that no commit was pushed. A job is not labeled applied unless its repair was published.none

A successful fix does not open a second pull request and does not create a new branch. After the push, the usual synchronize review still runs.

A wrong finding's reply is posted by the service, not by a file the model writes. The next review reads that reply.

Retry only with another comment

Do not use GitHub Re-run on the implement-agent check. Re-run does not start a fix. Comment again.

Limits:

  • A second write while one write is queued or running on the same pull request is refused. Wait until that run finishes.
  • Three admitted starts are allowed against one head commit. The fourth is refused. A failed run and a run that commits nothing still count. A refused request does not. Delivering the same comment twice does not count as another start.
  • A new commit on the pull request head resets that count.
  • A closed or merged pull request cannot be fixed. Open a follow-up pull request and comment there if the work still needs to land.