Menu
Summarize a spec or current changes into a format suitable for sharing on Slack. Use when creating a summary for team communication.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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.
| name | summarize |
| description | Summarize a spec or current changes into a format suitable for sharing on Slack. Use when creating a summary for team communication. |
Summarize the given spec or current changes into a format suitable for sharing on Slack.
Read the spec file or use git diff to understand the current changes if no spec is provided.
Output the summary in this exact format:
**Problem:** Right now, we ...
- <bullet point explaining issue>
- <bullet point explaining issue>
- ...
**Solution:** <one sentence explaining the solution>
- <bullet point explaining change>
- <bullet point explaining change>
- ...
Guidelines: