Menu
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
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
| name | dyad:pr-fix |
| description | Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks. |
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
$ARGUMENTS: Optional PR number or URL. If not provided, uses the current branch's PR.You MUST use the TaskCreate and TaskUpdate tools to track your progress. At the start, create tasks for each step below. Mark each task as in_progress when you start it and completed when you finish. This ensures you complete ALL steps.
When making decisions about review comments, consult rules/product-principles.md. Use these principles to resolve ambiguous or subjective feedback autonomously. Only flag issues for human attention when the product principles do not provide enough guidance to make a decision.
This is a meta-skill that orchestrates two sub-skills to comprehensively fix PR issues.
Run /dyad:pr-fix:comments to handle all unresolved review comments:
Run /dyad:pr-fix:actions to handle failing CI checks:
Run /dyad:pr-push to commit and push all changes:
Post Summary Comment:
After both sub-skills complete, post a comment on the PR with a consolidated summary using gh pr comment. The comment should include:
<details> tags to collapse verbose details (e.g., full error messages, lengthy explanations)Error handling: If gh pr comment fails (e.g., due to network issues, rate limits, or permissions), log a warning but do not fail the entire skill if the underlying fixes were successful. The comment is informational and should not block a successful run.
Example formats:
Success:
## ✅ Claude Code completed successfully
### Summary
- Fixed 2 review comments
- Resolved 1 CI failure (lint error in `src/foo.ts`)
<details>
<summary>Details</summary>
... detailed information here ...
</details>
---
[Workflow run](https://github.com/dyad-sh/dyad/actions/runs/12345678)
Failure:
## ❌ Claude Code failed
### Summary
- Attempted to fix 2 review comments
- Failed to resolve 1 CI failure (lint error in `src/foo.ts`)
<details>
<summary>Error Details</summary>
**Error:** `lint` command failed with exit code 1.
... linter output ...
</details>
---
[Workflow run](https://github.com/dyad-sh/dyad/actions/runs/12345678)
Note: Include a link to the workflow run at the end. If the GITHUB_REPOSITORY and GITHUB_RUN_ID environment variables are available, use them to construct the URL: https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID. If these environment variables are not set, omit the workflow run link.
Commit any uncommitted changes, run lint checks, fix any issues, and push the current branch.
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.
Fix failing CI checks and GitHub Actions on a Pull Request.
Read all unresolved GitHub PR comments from trusted authors and address or resolve them appropriately.
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.
Promote the latest pre-release to a stable release by creating a release branch, bumping the version, and pushing.