Ryuu's Skills

Delivery Modes

Choose whether the agent hands work back unstaged or opens pull requests itself.

The delivery mode decides who publishes the work. There are two, and every skill that could commit, push or post reads the same one. delivery.md states both in full, and every skill defers to it.

Hands-Off Mode

This is the default. Nothing is staged, committed, pushed or posted for you. Work lands unstaged on a feat/* branch, the reply suggests one commit message, and the rest is yours.

PRs Mode

The agent that owns a task commits its verified work, pushes the task branch and opens the PR, or the next layer of a stack. Subagents and Codex arms still leave their work unstaged for that owner. It hands a PR back only once every check passes and the branch merges cleanly into its base. A failing check or a conflict is its next fix, not yours. Merging stays with you.

In prs mode you can also turn on reviewer extensions, one per review bot. They run inside each review fix round and decide when a PR is ready to hand back. The linear extension works on a task that names a Linear issue: it names the branch after the issue, links the PR to it, and moves it to the team's code review status.

A task you start without /plans, from custom instructions or a Linear issue, gets the same loop. Once the agent opens its PR, the same thread babysits it through the reviewer round and hands it back at the point a /plans do thread would. It pushes only to branches it created itself or that you name, so a teammate's branch stays untouched. Owners in prs mode has the detail.

What Each Needs

  • Hands-off mode needs nothing beyond the install.
  • In prs mode you need a GitHub remote and an authenticated gh. With gh stack installed, stacked plans go up as a GitHub stack, and skills publish refuses a version older than 0.2.0. Without it, each layer opens with gh pr create --base <parent>.
  • The greptile extension needs prs mode, and Greptile reviewing the repo.
  • The coderabbit extension needs prs mode, and CodeRabbit reviewing the repo.
  • The macroscope extension needs prs mode, and Macroscope reviewing the repo.
  • The linear extension needs prs mode, and the Linear MCP in the agent. Without it, the handback names each issue and its PR for you to link.
  • Babysitting a PR, in either mode, needs Bun, which runs the skills pr watch watcher.

Turn Them On

Each choice is one flag. The installer saves it to ~/.agents/skills.conf and keeps it on reruns.

./install.sh --with prs
./install.sh --with greptile
./install.sh --with coderabbit
./install.sh --with macroscope
./install.sh --with linear
./install.sh --without greptile --without coderabbit --without macroscope --without linear --without prs

The first line turns on prs mode. The next four each turn on an extension, which switches on prs mode with it. The last goes back to hands-off, whichever of the four you saved. Leave one out while it is saved and the installer refuses with install.sh: <name> requires prs mode, so hands-off needs --without <name> too.

install.sh installs the reviewer extensions with the rest of the skills. Each one stays inactive until the config lists it.

With AGENT_RULES set, the installer writes strengthening and neutral rule changes for the new mode. At a terminal, --with prs lists the weakening ones, such as dropping the publishing denies, ticked for you to confirm. Untick one to keep it as an override. A non-terminal run names them on left lines for you to apply by hand. With the key unset or the settings file refused, paste the set --verbose prints instead.

On this page