Review and Triage
Configure Mogplex for pull request review, issue triage, CI failure investigation, GitHub mentions, and follow-up edits.
Review and triage are the most common hosted Mogplex workflows.
They share setup, but they should not use the same agent role by default.
Pick the right job shape
| Job | Best starting surface |
|---|---|
| Every PR in one repo should be reviewed | Assignments |
| Every PR event in one installation should wake a reviewer | Triggers |
| Review should branch into an edit step only when findings are real | Automations |
| New issues need labeling, reproduction guidance, or routing | Assignments or Triggers |
| A human wants to ask from a PR or issue thread | GitHub mention routing |
| CI failure should be investigated and optionally fixed | Assignments, Triggers, or Automations |
Agent roles
Use review when the agent should inspect code changes and produce findings.
Use triage when the agent should understand a thread or event, classify it,
respond, label, or decide the next step.
Use edit when the graph has already decided code should be changed.
That split keeps mutation explicit. A reviewer can report findings, while a follow-up edit node can apply changes only after the workflow decides it should.
Common patterns
Standing PR review
Use an Assignment when one repo should always use the same review behavior. This keeps the repo as the durable unit of responsibility.
Lightweight event review
Use a Trigger when a GitHub event should wake one review agent without a workflow graph.
Review then fix
Use an Automation when the route should:
- review first
- branch on whether findings are real
- edit only on the fix branch
- keep draft changes separate until the workflow is published
Issue triage
Use a triage agent for new issues and issue comments. The agent should
classify, summarize, request missing information, route, or answer. It should
not be forced into code-review behavior unless the issue explicitly carries a
diff or reproduction branch.
GitHub mentions
Use exact mention syntax:
@mogplex summarize the failing check
@mogplex/triage label this and suggest next steps
@mogplex/reviewer review this diff with extra attention to authFor targeted mentions, the part after / must match an agent slug.
After work starts
Use Observability to answer:
- did the job run?
- did it fail, defer, suppress, or queue?
- what model and tools were used?
- what did it cost?
- which sandbox or GitHub object was involved?
If no run exists, go back to Routing and check setup before inspecting runtime detail.