// This skill should be used when the user asks to "QA changes", "verify this works", "test the build", "check if this runs", "validate changes in tmux", or wants end-to-end verification of code changes by running builds, tests, and applications in tmux.
Extract design DNA from a website into a reusable specification with steerable variables
YOU MUST use this skill for anything involving past Claude Code conversations in ~/.claude/projects/: when the conversation starts with 'this session is being continued from a previous conversation that ran out of context', or to recover context from a previous conversation, or to discover/catalog which conversations exist (by date, project, message count), or to search and read past conversation logs. One entry point for cataloging, searching, and rendering Claude Code JSONL transcripts.
Always consult before any Google Workspace operation via the `gws` CLI: sending or reading Gmail and triaging the inbox, Calendar events and agendas, Docs, Drive files and folders, Sheets, Slides, Forms, and adding, listing, or completing Tasks, reminders, and to-dos. Routes to per-service reference files for auth, flags, and command syntax.
Always consult before drafting any human-facing prose: messages, emails, pull request descriptions, GitHub issues, Reddit posts, agendas, documents, code review comments, bug reports, release notes, or any other text a person will read. Enforces direct, warm, unfilled tone; removes AI tells; runs a self-audit before delivery. Skip ONLY when the task is operational (calling an API, running a CLI) rather than composing prose.
Always consult before opening, reading, navigating, scraping, fetching, or screenshotting any URL or webpage. Handles browser automation, JavaScript-rendered content, form filling, dynamic page interaction, and structured extraction in ways native HTTP fetch cannot. Skip ONLY for raw-text or JSON endpoints where a single WebFetch suffices.
Always consult before writing, scoring, or rewriting any SKILL.md description field. Provides the rubric, template, and apply script that handle YAML safety and produce a backup on each write.
| name | tmux-qa |
| description | This skill should be used when the user asks to "QA changes", "verify this works", "test the build", "check if this runs", "validate changes in tmux", or wants end-to-end verification of code changes by running builds, tests, and applications in tmux. |
| context | fork |
| agent | tmux-qa |
Verify the code changes in this project work correctly.
Scope: $ARGUMENTS
If no scope was provided, read the recent changeset to determine what needs verification. Detect the build system, run the appropriate build/test/run commands in tmux, and report results.
Visibility: If invoked from inside a tmux session ($TMUX set), the agent MUST split a new pane into the user's current session so they can watch the work live. Outside tmux, fall back to a detached qa-<timestamp> session and print the tmux attach command so the user can hook in. Either way, every build/test/run command goes through tmux send-keys — never bypass with raw Bash even for non-interactive commands.
