libretto

Read-only Libretto workflow for diagnosing live browser state without clicks, typing, navigation, or mutation requests.

Browser automation CLI for building, maintaining, and running browser automation workflows by inspecting live pages and prototyping interactions.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Automate user-installed Electron desktop apps (Slack, Discord, VS Code, Notion, Figma, Spotify, etc.) via CDP using this repo's Libretto CLI. Use when the task is to control a local desktop app on the user's machine, not this repo's own Electron app. Triggers: "desktop Slack app", "connect to Electron app", "remote-debugging-port", "CDP desktop app", "automate VS Code desktop app".

Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.

Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.

Commit and push changes, creating or updating a PR as needed. Use for standard push workflow.

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.

Create a visual explanation of the current session diff as a single HTML page and show it in a native Glimpse window. Use when the user wants a visual walkthrough of local code changes instead of a plain text diff.

Write and edit test files that model real user flows. Use when creating, modifying, or reviewing test files.

Resolve Git merge, rebase, or cherry-pick conflicts by preserving intent from both sides. Use when unmerged paths or conflict markers are present, especially when you must inspect the PR title and description tied to conflicting commits before choosing a resolution.

Design and implement command-line interfaces with subcommand-scoped help, actionable success output, and debuggable failure output. Use when creating or modifying CLI commands, argument parsing, help and usage text, exit codes, or command UX for humans and agents.

Review a spec for under-specified areas, bugs, and adherence to the spec requirements in this skill. Use when asked to review, critique, or check a spec.

Address PR review comments systematically. Use when responding to code review feedback on a pull request.

Get nicely formatted output of the last review comments on a PR. Used internally by other skills.

Implement a single phase of a spec. Use when given a spec file and a phase number to implement.

Guide for writing effective system prompts for LLM agents. Use when creating or editing system prompts for applications, agent configurations, or development tools.

Expert code review specializing in simplicity and correctness. Use after completing implementations to ensure code quality.

Summarize a spec or current changes into a format suitable for sharing on Slack. Use when creating a summary for team communication.

Guide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.