poteto-mode: fetch latest main before starting work or spawning agents

[0xTenable]

What

Adds one non-negotiable trigger to pstack's poteto-mode skill:

Starting development or spawning code-writing agents → git fetch origin main first, then branch or rebase onto it so work starts from latest main. A worker inherits the checkout or base branch it spawns from; a stale base hands every worker a stale start.

Why

poteto-mode delegates code-writing to spawned workers (cloud agents, worktree-isolated agents). Those workers inherit whatever base the spawning checkout or configured base branch points at. When local main is stale, every spawned worker starts behind origin, and the drift surfaces later as avoidable merge conflicts and re-verification. Making the fetch a named trigger puts it ahead of every playbook instead of relying on each agent to remember.

Placed as the first remaining trigger since it gates all development work, and worded harness-neutrally so ports to other harnesses carry it unchanged.

Test plan

Text-only change to a skill definition. Verified the bullet renders in the trigger list and survives the skill's port-time rewrites.

Written with Devin.

---

Note

Low Risk
Documentation-only change to agent skill triggers; no runtime, auth, or application code.

Overview
Adds a first non-negotiable in poteto-mode: before starting development or spawning code-writing agents, run git fetch origin main and branch or rebase onto current main so workers do not inherit a stale base.

The bullet is harness-neutral (checkout/base branch wording) and documents why it matters (spawned workers copy the spawning context, so drift shows up later as merge pain and re-verification).

^{Reviewed by Cursor Bugbot for commit 5a1e13d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit 5a1e13d. Configure here.}

[cursor]

Trigger prose joins clauses with semicolon

Low Severity · Bugbot Rules

The new remaining-trigger sentence joins two independent clauses with a semicolon, which pstack skill prose forbids under unslop punctuation. Sibling triggers in this list already use a period for that split. This is the only semicolon in SKILL.md.

 

^{Triggered by learned rule: pstack skill prose follows unslop punctuation}

^{Reviewed by Cursor Bugbot for commit 5a1e13d. Configure here.}