Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
0xTenable wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −0
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions pstack/skills/poteto-mode/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ The Principles section below grounds every trigger. In your reply, name each pri

Remaining triggers:

- 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.

@cursor cursor Bot Sep 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

Triggered by learned rule: pstack skill prose follows unslop punctuation

Reviewed by Cursor Bugbot for commit 5a1e13d. Configure here.

- Nontrivial change, architecture decision, or "are we sure?" → the **how** skill.
- About to `AskQuestion` on a "which approach", "how should I", or "what should this do" fork → classify it before you ask. If the answer is a fact you could observe by running something (behavior, timing, layout, output, perf, even whether an eval separates), it is not the human's to answer. Sketch it via the Prototype playbook (`playbooks/prototype.md`) and let the result decide. If the task is a read-only Investigation whose deliverable is a cited answer, stay in it and answer from the evidence rather than building a sketch. Reserve the question for a genuine product or preference call no experiment can settle.
- Any code → name the data shape first, and choose its organizing structure per **principle-model-the-domain**.
Expand Down