Your first agent session

This tutorial assumes Sepo is installed and responding. You’ll go from asking a question to landing a reviewed pull request without leaving GitHub.

Ask a question

Mention @sepo-agent anywhere you can write a comment — an issue, a pull request, or a discussion. A free-form mention lets the router pick the best route:

@sepo-agent how does review synthesis work in this repo?

Sepo reacts with 👀 while it works and posts the answer in the same thread, so the exchange stays part of the record anyone can find later.

Turn an issue into a pull request

When you want code rather than an answer, use an explicit route. On an issue describing the change:

@sepo-agent /implement

Sepo works in GitHub Actions, pushes a branch, and opens a draft PR linked back to the issue. The full route list — /answer, /implement, /review, /fix-pr, /orchestrate, and more — is in Quick start, and each route’s behavior is detailed in Agent actions.

Run the review loop

On the pull request:

@sepo-agent /review

runs the dual-agent review flow and posts a synthesized verdict. If it finds issues, follow up with:

@sepo-agent /fix-pr

and Sepo pushes fixes to the same branch. For bounded multi-step work, /orchestrate keeps the implement → review → fix loop going until the review passes or a stop condition hits — see Supported workflows.

What accumulates

Each session leaves the repository a little more capable: run context lands on the agent/memory branch, and lessons from your reviews become rubrics that steer future implementations. How memory works and Rubrics explain the mechanics.