branches
FreeWhere your work goes (a branch named agent-<name>), how to name it, what must be true before you finish, and how to push it when you are asked to.
The English summary is being prepared. Showing the original description.
Answer where a maintainer calls you with /agent, on an issue or a pull request; and on your own pull request, checks that turned red and a conflict with its base branch.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
What follows the command says why you are here: a maintainer called you with /agent on an issue or a pull request, or a pull request of yours has a red check or conflicts with its base branch. Nobody will answer you here: never ask, decide yourself.
First read the whole issue or pull request again, its discussion and a pull request's changes, not only what is below: a comment may answer an earlier one, and one may already be answered. If it cannot be read, show an error to the user saying why and stop.
Post on it the way your git host skill says. Each time a new comment, never an edit of an earlier one: a new comment reaches people by email, an edit reaches nobody.
If what came will take you more than about 5 minutes, first post a short comment: what you are going to do, and that you will comment here when finished.
On someone else's pull request you are on its branch: your changes go there, never in a pull request of your own. One from a fork you cannot push to: answer, and say that you cannot change it.
For each call, comment or review: do what it asks, answer it, or leave it, and say which and why.
A red check: read why it failed, fix it and push. One that fails for a reason outside your change: say so and leave it.
A conflict with the base branch: merge the base branch into your branch, resolve it, and push. Never rebase and never force a push. A conflict you cannot resolve with confidence: say what conflicts, and leave it for a person.
When you are done, post your answer: each thing below and what you did about it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Where your work goes (a branch named agent-<name>), how to name it, what must be true before you finish, and how to push it when you are asked to.
The English summary is being prepared. Showing the original description.
A real browser you drive from the shell, to see or act on a web page (open it, read it, click, type, take a screenshot), such as checking that the app you changed works.
The English summary is being prepared. Showing the original description.
Post a message to the team's Discord channel from the shell, when a task asks you to tell people something there.
The English summary is being prepared. Showing the original description.
The project's git host is GitHub: how to open your pull request when you are asked to, how to land it, and how to read and close the project's issues.
The English summary is being prepared. Showing the original description.
The record of every run agents made on this project — what was asked, where the work went, how it ended, what the agent said — where it lives, how to read it, and when to look back before you work.
The English summary is being prepared. Showing the original description.
Refactor a part of the code to make it as maintainable as possible.
The English summary is being prepared. Showing the original description.