Claude Skills by dyad-sh

Add one or more AI models to the language model constants file, researching specs from official docs.

Check GitHub Actions workflow runs from the past day, identify severe or consistent failures, and file an issue if actionable problems are found.

Map a minified error stack trace from a production Dyad build back to original source locations using source maps.

Debug E2E tests by taking screenshots at key points to visually inspect application state.

Deep multi-agent code review run locally — a fleet of parallel finder agents reviews the diff from independent angles, then adversarial verifier agents reproduce each finding before it is reported. Local equivalent of /code-review ultra. Use when the user asks for a deep, thorough, or multi-agent review of their branch, working diff, or a PR before merging. Usage: /deep-review (reviews current branch vs main, including uncommitted changes) or /deep-review <PR-number>.

Root-cause flaky or failing E2E tests from a specific CI run by downloading and analyzing the Playwright HTML report (traces, screenshots, errors). Use this when given a GitHub Actions run URL and asked to investigate failures. Diagnose from report artifacts first, then rebuild and rerun the affected E2E tests locally after making fixes.

Automatically gather flaky E2E tests from recent CI runs on the main branch and from recent PRs by wwwillchen/keppo-bot/dyad-assistant, then deflake them.

Identify and fix flaky E2E tests by running them repeatedly and investigating failures.

Rebase E2E test snapshots based on failed tests from the PR comments.

Turn customer feedback (usually an email) into discrete GitHub issues. Checks for duplicates, proposes new issues for approval, creates them, and drafts a reply email.

Create a plan to fix a GitHub issue, then implement it locally.

Multi-agent code review system that spawns three independent Claude sub-agents to review PR diffs. Each agent receives files in different randomized order to reduce ordering bias. One agent focuses specifically on code health and maintainability. Issues are validated using reasoned analysis rather than simple vote counting. Reports merge verdict (YES / NOT SURE / NO). Automatically deduplicates against existing PR comments. Always posts a summary (even if no new issues), with low priority iss...

Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.

Diagnose and fix failing CI checks on a pull request from its latest GitHub Actions CI run. Use when PR CI has E2E/Playwright failures, macOS or Windows unit-test failures, or presubmit/type/build failures; analyzes the exact run logs and artifacts, invokes dyad:deflake-e2e-from-run for E2E failures, reproduces targeted unit tests locally, and publishes the fixes.

Read all unresolved GitHub PR comments from trusted authors and address or resolve them appropriately.

Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.

Publish local work by committing changes, running checks, pushing the branch, and creating or refreshing a GitHub PR with a reviewer-useful description.

Rebase the current branch on the latest upstream changes, resolve conflicts, and push.

Record a visual demonstration of the key feature of this PR using screenshots and add it as a new comment to the PR.

Promote the latest pre-release to a stable release by creating a release branch, bumping the version, and pushing.

Review the current session for errors, issues, snags, and hard-won knowledge, then update the rules/ files (or AGENTS.md if no suitable rule file exists) with actionable learnings.

Team-based PR review using Claude Code swarm. Spawns three specialized teammates (correctness expert, code health expert, UX wizard) who review the PR diff, discuss findings with each other, and reach consensus on real issues. Posts a summary with merge verdict and inline comments for HIGH/MEDIUM issues.

Swarm planning session with PM, UX, and Engineering agents who debate an idea, ask clarifying questions, and produce a detailed spec written to plans/$plan-name.md.