libretto

address-review

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

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.

errore

errore is Go-style error handling for TypeScript: return errors instead of throwing them. Instead of Go's two-value tuple (val, err), functions return a single Error | T union. Instead of checking err != nil, you check instanceof Error. TypeScript narrows the type automatically — forget to check and your code won't compile. No wrapper types, no Result monads, just unions and instanceof. The errore npm package provides helper utilities (createTaggedError, tryAsync, matchError, findCause, partition) but the core pattern is zero-dependency. Benefits: every error is visible in the return type, callers can't forget to handle errors, flat control flow with early returns instead of nested try-catch, and errors carry typed properties with cause chains for debugging. ALWAYS read this skill when a repo uses the errore "errors as values" convention (errore.org). ALWAYS use errore for new TypeScript projects.

external-electron-apps

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

fix-merge-conflicts

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.

Testing & QA Featured

generate-spec

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

get-pr-reviews

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

glimpse-changes

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.

Testing & QA Featured

implement-spec

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

improve-codebase-architecture

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.

prompting

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

push-everything

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

Show all 23 bundled skills

push

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

review

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

spec-review

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.

summarize

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

Data & Documents Featured

technical-writing

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.

turborepo

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.

Data & Documents Featured

update-docs

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

writing-tests

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

Web & Frontend Featured

dev-browser

Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.