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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Your work goes on a branch named agent-<name>, unless whoever started you continued you on another. It stays on this machine until you are asked to push it.
Run the branches command inside your checkout, always by its full name: npx @openagt/skill-branches@0.1. status, name and push (with no flag) are yours; the rest are the caller's.
npx @openagt/skill-branches@0.1 status
It prints JSON; branch is the branch you are on.
A branch starting with agent-. Its checkout is your whole workspace: read and write only there. Dependency files and skill folders are links to the user's copies: never edit them. If something you need is outside your checkout, say so and stop.
Before your first change, name the session with [a-z0-9-]+, starting with a letter or digit, saying what the work is, unless your branch already differs from path's last segment: then it is named, keep it.
npx @openagt/skill-branches@0.1 name <name>
It renames your branch to agent-<name> and prints it in branch: agent-<name>-2, -3, … when <name> was taken; a name outside [a-z0-9-]+ is refused as invalid-name.
Any other branch. If the checkout sits under .branches/, you were put on this branch on purpose: stay on it, do not name it. Otherwise you are in a plain clone on someone else's branch. Before your first change, create your own and switch to it, <name> as above (another if it exists, locally or on origin):
git switch -c agent-<name>
From then on, work as on an agent- branch; nothing in a plain clone is a link.
Nothing is committed for you.
npx @openagt/skill-branches@0.1 status
It must report "clean": true. clean is false while anything is uncommitted or untracked: commit or delete what you added; if what remains is not yours, say so and finish.
Only when your task or the person asks you to push or publish your work, and once clean:
npx @openagt/skill-branches@0.1 push
It pushes your branch to origin and prints it in branch. clean false is refused as dirty: commit or delete first.
Only when the person asks you to merge your work into the project's main branch, and once clean:
npx @openagt/skill-branches@0.1 merge <your branch>
It merges your branch into the main branch, in the project's own folder. A conflict changes nothing and names the files in files: say so and stop. Your checkout and your branch stay.
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.
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.
Find the parts of the code that need refactoring and put their maintainability and security work on the agent queue. Queues only.
The English summary is being prepared. Showing the original description.