jolo

Browse, screenshot, or visually verify a local web app using the pre-installed browser-check and playwright-cli (never install your own browser). Use when asked to screenshot, browse, open/view a page, check the UI, or confirm the site is running.

Prioritize open TODO items by effort and impact, recommend what to work on next. Add the `full` keyword to also weigh project notes and stash context.

Resume a session — read the paste-back handoff note to recall what we last worked on, falling back to a git+TODO status when none exists. Add the `full` keyword to also deep-scan project notes and memory.

Write the paste-back handoff note (scratch/resume-session.md) so the next session can hit the ground running. Add the `full` keyword to also save durable knowledge to denote notes + TODO and commit.

Get oriented on host-level, cross-project knowledge by reading the stash README map. Use when starting fresh in a container, or when you need the lay of the land for hardware, dotfiles/preferences, Emacs, Linux, or cross-project conventions that live outside the current repo.

Work autonomously while the user is away. Create multiple feature branches sequentially, each with a self-contained improvement.

Structured workflow for feature-sized or risky changes: short intake questions, create a branch, use TDD where applicable, commit frequently, get an external agent review, fix issues, then get a second external review and optionally open a PR. Use when the user says a task is big, multi-step, high-risk, or explicitly wants TDD, frequent commits, or multi-agent review.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Scaffold a new frontend web project with Vite, Tailwind CSS, and standard configuration. Supports React, Svelte, and Vue frameworks.

Run pragmatic tests first, then get a second-opinion code review from another AI agent (claude, gemini, or codex) using the current git diff. Use when you want a fresh, correctness-focused review without heavy setup.

Compare two or more document versions and provide a narrative summary of meaningful differences. Use when the user wants a human-readable summary of changes across versions (A/B/C), change impacts, regressions, or missing content, without a line-by-line diff or rewrite.

Critique and improve prose documents while preserving the author's voice. Use when the user asks to review, critique, or sanity-check docs, READMEs, proposals, blog posts, product notes, or other writing, and they want feedback, gaps, and suggestions rather than a full rewrite.

Plan and guide host-machine operations that must be run manually outside this devcontainer. Use when the task targets local/remote hosts (not the current workspace container), especially SSH/mosh/tmux/terminal/network setup.

Use when the user explicitly wants to save a cross-project lesson, incident, convention, or gotcha to the shared stash denote notes.

Web research workflow that collects sources and summarizes findings into an org file. Use when the user asks to research a topic, compare sources, or gather references.

Reconcile project docs (MEMORY.org, TODO.org, AGENTS.md) with the current state of the code and recent commits.