19.7k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill dyad-sh/dyad --skill pr-fix-actions- SKILL.md3.2 KB
Overview
This skill fixes failing CI checks and GitHub Actions on a Pull Request. It inspects the PR, identifies failing checks (lint, types, unit tests, E2E, build), applies targeted fixes, and prepares a clean commit ready to push. It produces a concise summary of what was fixed and any remaining issues that need human attention.
How this skill works
The skill locates the target PR (explicit PR number/URL or the current branch's PR) and runs GitHub CLI checks to list failing jobs. It runs local commands to reproduce and resolve failures: lint/format auto-fixes, TypeScript fixes, unit test debugging, build fixes, and E2E troubleshooting with rebuilds and snapshot handling. All progress is tracked via task creation and updates, and changes are committed for push.
When to use it
- A pull request shows failing CI checks in GitHub Actions
- You need to reproduce CI failures locally to investigate root causes
- Lint or formatting checks are blocking merge
- TypeScript errors or build failures prevent the PR from passing
- Playwright/E2E tests are failing or snapshots need rebase
Best practices
- Start by creating tasks for each step and update their status as you work
- Always build the app before running E2E tests and rebuild after code changes
- Auto-fix lint and formatting first, then re-run checks to narrow failures
- Reproduce failing unit tests locally with the exact test pattern to debug
- Use clear commit messages summarizing each fix and include co-author when required
Example use cases
- A PR fails only on lint and formatting: run lint:fix and fmt, review changes, commit
- Type errors introduced by a refactor: run ts, fix types in files, re-run type checks
- A flaky unit test fails in CI: reproduce locally, fix race condition or update test
- Playwright snapshots changed after UI updates: rebase snapshots using the e2e rebase flow and rebuild
- Build errors after dependency updates: run npm run build, fix imports or configuration, and re-run CI
FAQ
The skill will inform you that no PR exists and stop; create a PR first or pass a PR number/URL as an argument.
Do I need to rebuild before every E2E test run?
Yes. E2E tests run against the built app. Rebuild whenever you change application code outside e2e-tests.