scaryrawr

Draw what an app's user sees as a Mermaid statechart from a TLA+ model. States are gray if they work, red if still wrong, and green if fixed. Each bug TLC finds is a numbered path. Use for /statechart, "show the PM the bug", or to turn an agreed chart into a…

Answer explicitly typed /poteto-help requests or help questions about pstack setup, usage, skills, playbooks, and principles. Recommend a prompt without executing it. Not for generic coding, debugging, design, review, or implementation work.

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.

Use when implementing a feature, fixing a bug, changing behavior, or refactoring code, including ordinary implement/fix/change requests that do not ask for proof. Check the actual acceptance condition and return proportionate evidence by default, or name the…

Use for performing Azure DevOps work — create, inspect, review, discuss, comment on, vote on, or manage pull requests; find, query, create, update, and link Azure Boards work items (including building WIQL queries); parse and route dev.azure.com or…

Drive an Azure DevOps pull request from local changes through completion, including review threads, required policies, conflicts, safe auto-complete, and continued monitoring for new failures. Use when asked to "agent merge" an ADO PR, create an Azure DevOps…

Record agent-driven screen demos and edit video or audio with local FFmpeg. Use for screen recording or desktop capture while computer-use tools drive a workflow; trimming setup or dead time; putting videos side by side; adding captions or subtitles;…

Find mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Use for /correct or…

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each…

Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, model-check this race, prove this…

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.

Catch the user up on what changed in this chat since their last message, in plain words and small visuals. List every item waiting on them with what they need to decide it from the reply alone. Use for /ketchup.

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in…

Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

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.

Apply when writing, changing, reviewing, or keeping tests. Call the code as its users do and assert an independently specified result or effect. Rewrite tests that would pass when the behavior they claim to prove is broken.

Review pull requests in this repository for shared Azure authentication policy, shell compatibility, credential isolation, and configuration-write regressions.

Review fish wrapper changes for token injection consistency and safe argument passthrough.

Validate fish wrapper and completion changes with syntax and smoke checks.

Perform a thorough code review of diffs or branch comparisons for correctness, structure, regression risk, and edge-case coverage. Use when the user asks to review uncommitted changes, inspect a PR/diff, compare a branch to default, or audit recent changes…

Use this skill to create, revise, package, evaluate, or optimize GitHub Copilot skills and reusable SKILL.md-based agent instructions. Use it whenever the user wants a new Copilot skill, edits to an existing skill, eval/test prompts, skill benchmarking, skill…

Create or improve AGENTS.md and project agent-skill guidance for a repository. Use when the user asks to initialize, bootstrap, or set up agent instructions, repo guidelines, AGENTS.md, or reusable skills. Discovers repo structure, commands, existing…

Code review an Azure DevOps pull request

When users share links (such as visualstudio.com or dev.azure.com) and/or mention Azure DevOps, use the Azure DevOps CLI to interact with work items, pull requests (PRs), repositories, and more.

Remote control tmux sessions for interactive CLIs (python, gdb, etc.) by sending keystrokes and scraping pane output.

Use this skill when smahtiepants MCP tools are available and a task depends on current documentation for a library, framework, language, runtime, API, or CLI tool (for example React, Express, Node, Python, Rust, CSS, Docker, Git, or Bun). Prefer the MCP tools…

Use this skill before answering questions or writing code that depends on a specific library, framework, language, runtime, or CLI tool (e.g. React, Express, Node, Python, Rust, CSS, Docker, Git, Bun). Your training data has a cutoff and APIs change, get…

Update fish shell completions for the GitHub Copilot CLI based on its current help output. Use when asked to update, sync, or refresh completions, or when the CLI has been updated and completions need to match the latest flags, subcommands, and help topics.

Run fish syntax and completion validation for this repository.

Review fish wrapper changes for token injection consistency and safe argument passthrough.

Validate fish wrapper and completion changes with syntax and smoke checks.

Audit or prepare this GNOME Shell extension for extensions.gnome.org review. Use after changing extension lifecycle, asynchronous work, signals, GLib sources, preferences, GSettings, supported Shell versions, packaging, or before a release or EGO submission.

Update the Fish and Zsh completion implementations to match the current Copilot CLI interface. Use when asked to update, refresh, or sync completions, or when CLI options, commands, models, or help topics change.

Update the Zsh completion function (_copilot) to match the current copilot CLI interface. Use this skill when the user asks to update, refresh, or sync completions, or when new copilot CLI options, commands, or models need to be added to the completion file.

Use this skill for explicit or adaptive end-of-task pi-digivolve reflection when deciding whether durable repo-specific guidance, AGENTS.md, pi skills, or in-repo SKILL.md files are stale, missing, or should be updated.