Skip to content

Jrecos/omp-pstack / skills/poteto-mode

poteto-mode

Unverified

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

FileKindSize
SKILL.mdskill md25.2 KB
playbooks/authoring-a-skill.mdmarkdown829 B
playbooks/autonomous-run.mdmarkdown2.1 KB
playbooks/autopilot-full.mdmarkdown6.9 KB
playbooks/autopilot-stack.mdmarkdown877 B
playbooks/babysit.mdmarkdown8.3 KB
playbooks/bug-fix.mdmarkdown2.3 KB
playbooks/eval.mdmarkdown2.6 KB
playbooks/feature.mdmarkdown7.0 KB
playbooks/hillclimb.mdmarkdown4.3 KB
playbooks/investigation.mdmarkdown928 B
playbooks/multi-phase-plan.mdmarkdown14.0 KB
playbooks/opening-a-pr.mdmarkdown6.6 KB
playbooks/orchestrate.mdmarkdown4.8 KB
playbooks/pause-safely.mdmarkdown1.8 KB
playbooks/perf-issue.mdmarkdown1.4 KB
playbooks/prototype.mdmarkdown2.1 KB
playbooks/refactoring.mdmarkdown3.4 KB
playbooks/runtime-forensics.mdmarkdown1.3 KB
playbooks/session-pickup.mdmarkdown2.2 KB
playbooks/shipping.mdmarkdown5.9 KB
playbooks/trace-forensics.mdmarkdown1.8 KB
playbooks/visual-parity.mdmarkdown1.2 KB
playbooks/worktree-cleanup.mdmarkdown3.6 KB
references/bugbot-triage.mdmarkdown9.4 KB
references/omp-control-cli.mdmarkdown6.2 KB
references/omp-control-ui.mdmarkdown7.0 KB
references/omp-create-skill.mdmarkdown3.6 KB
references/omp-deslop.mdmarkdown1.1 KB
scripts/check-plan.mjsexecutablescript8.1 KB
scripts/check-plan.test.tsscript4.0 KB
scripts/watch-pr/cli.test.tsscript6.0 KB
scripts/watch-pr/cli.tsscript6.8 KB
scripts/watch-pr/fakes.test-helper.tsscript3.3 KB
scripts/watch-pr/github.test.tsscript15.8 KB
scripts/watch-pr/github.tsscript25.0 KB
scripts/watch-pr/policy.test.tsscript17.6 KB
scripts/watch-pr/policy.tsscript25.5 KB
scripts/watch-pr/render.tsscript7.2 KB
scripts/watch-pr/tsconfig.jsonconfig270 B
scripts/watch-pr/types.compile.tsscript2.2 KB
scripts/watch-pr/types.tsscript12.7 KB
scripts/watch-pr/watch-prexecutablescript906 B
scripts/worktree-audit.tsexecutablescript21.9 KB

playbooks/opening-a-pr.md

View on GitHub
### Opening a PR

Invoked at the end of every other playbook.

**Worktree.** For writable coding, reuse an appropriate isolated checkout or create an explicit native worktree with `omp worktree add -b <branch> <path> <base>`. Resolve the intended PR base and verify the actual branch and cwd before writing. If a checkout contains unrelated changes or has an unclear state, leave it intact and create a fresh isolated worktree. Transfer only the task's changes. Never reset a checkout to discard work you have not accounted for. Check dependencies and environment files after clone fallback. Recheck private enablement per checkout. A main worktree does not isolate sibling workers or replace Docker.

**Optional startup.** Automatic main-session worktrees are source-assessed, not live-UI verified. If enabled locally, use `worktree.onStart=ask`, `worktree.onExit=keep`, and `worktree.cleanSource=false`. Startup begins from HEAD without source WIP. Failure warns and continues in the original cwd. Verify isolation before editing. Do not change global settings.

**Documentation.** Run the [Documentation completion gate](../SKILL.md#documentation-completion-gate) before commit, opening ready, marking ready, or declaring complete. Keep it in task todos before delivery. Include docs paths and exercised accuracy checks, or the concrete no-impact reason, in the final reply and `## Verification`. Unresolved required documentation blocks delivery.

**Commits.** Commit liberally. Rebase into small, ordered commits before opening PRs. Each commit is a future PR: landable, ordered to tell the story. Amend when the fix belongs in a just-made commit. New commit when separable. Commit bodies don't restate the subject.

**PRs.** Run the packaged deslop checklist (`../references/omp-deslop.md`) over the diff before commit and `/no-comments` before review. Write every PR title, description, and commit body with `/technical-writing`, then apply `/unslop`. Apply every technical-writing layer except Diátaxis. Use one word per action, keep articles, and prefer a plain verb to `-ing` where one works.

**Titles.** Conventional Commits `type(scope): subject`, no trailing period. Type such as `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, or `perf`. Scope is the area, such as `pstack` or `poteto-mode`. Subject is short, imperative, and names a real symbol when one carries the change, for example `fix(pstack): retarget opening-a-pr babysit trigger`.

**Descriptions.** The PR body is a one-minute briefing, not a lab notebook, for a reviewer who has the diff. It says why the change exists, what it leaves out, what it could break, and how you proved it works. Write short, simple sentences with few identifiers, no walls of text. The body becomes the squash commit body, so keep that commit under about 40 lines. Use `##` headings, not bold lead-ins, in this order, and drop a section with nothing to say:

- `## Why`: the problem and approach, 1–3 short sentences. No SHAs, rebase genealogy, or "based on main" preamble.
- `## What changed`: 1–3 short bullets. Name a real symbol or path only when it carries the change. Name both sides of a rename or retarget.
- `## Scope`: always. 1–3 short items on what it covers and what it deliberately leaves out (a follow-up, a known gap). No symbols, paths, or file-by-file essay.
- `## Tradeoffs`: only rejected alternatives a reviewer would otherwise ask about. Skip when there was no real choice.
- `## Blast Radius`: 1–2 sentences on who or what it touches and why that is safe or risky. If main is red, state the cost of leaving it red.
- `## Verification`: 1–3 bullets, each a real run path and its outcome. Perf: one primary number with its unit, `before → after`, and a link to the arena or swarm directory for the rest. No sample-size methodology, swarm recitals, or metric tables.

After the sections, attach videos or screenshots when they prove a claim. Full SHAs, swarm or arena lane recitals, lever-correction essays, file-by-file checklists, and "CLEAN" verdicts go in a linked artifact, not the body.

**Forge.** Resolve the forge before the first PR operation and keep that choice for create, edit, view, watch, and merge. GitHub CLI (`gh`) is the default. If `command -v origin` succeeds and Origin can resolve the repository, prefer `origin pr ...`. If Origin is absent or cannot resolve the repository, stay on `gh` and record the fallback. Do not require Graphite (`gt`).

**Built-in PR tool.** When the run provides a built-in PR tool, create, edit, retarget, and mark ready through it, never through a forge CLI. A CLI-made PR misses what the tool tracks. Use the resolved forge for everything the tool does not cover, and for every PR operation when the run has no such tool.

**Size and stacks.** Prefer five narrow PRs to one large PR. A stack is a base-branch chain. The root PR targets trunk. Each child branch rebases onto its parent's exact tip and its PR targets the parent branch. As a parent merges, move its child onto trunk per `playbooks/shipping.md` step 4. Without a built-in PR tool, per the resolved forge, create a child with `origin pr create --status open --base <parent-branch>` or `gh pr create --base <parent-branch>`, and retarget one with `origin pr edit <pr> --base <parent-branch>` or `gh pr edit <pr> --base <parent-branch>`. Branch from trunk only for independent work. Rebase on trunk before substantial stack work.

**Readiness.** Open every PR ready, never as a draft. A built-in PR tool can default to draft, so set `draft: false` on every creation call through it. With Origin, pass `--status open`. With `gh`, omit `--draft`. If a PR still opens as a draft, mark it ready through the PR tool, or run `origin pr ready <number>` or `gh pr ready <number>` according to the resolved forge. Run `origin pr view <number>` or `gh pr view <number>` before you refer to PR status.

**Babysit.** Opening a PR does not start a babysit. Post the URL and keep building. Finish the phase or stack first. Run a separate babysit pass only when the user asks for one after the whole stack exists. A babysit for each new PR stalls the build and spends checks on commits later waves restart. Push back when feedback drifts from intent.

A subagent that opens a PR runs `interrogate`, the packaged deslop checklist (`../references/omp-deslop.md`), and `/no-comments`, and posts the URL. It returns to the parent without babysitting, unless it is an Autopilot-full or Autopilot-stack owner. That owner's brief assigns the babysit loop and is the ask `playbooks/babysit.md` waits for. The owner starts the loop after its code-ready report, reports merge-ready, and is exempt from the rules here and in `playbooks/babysit.md` that hold babysitting until a whole stack is built.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall