dyad:pr-fix

Resolves GitHub pull request review comments and failing CI checks automatically.

21.4k|2.6k|Updated Apr 11, 2025
One-click install
npx skills add https://github.com/dyad-sh/dyad --skill dyad-pr-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dyad:pr-fix
Source: https://github.com/dyad-sh/dyad/tree/main/.claude/skills/pr-fix
Command: npx skills add https://github.com/dyad-sh/dyad --skill dyad-pr-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open pull requests often accumulate unresolved review comments and failing CI checks that require tedious manual triage. This Skill automates the full remediation loop so a PR can move toward merge without back-and-forth effort.

Core Features & Use Cases

  • Review Comment Resolution: Addresses valid code review concerns, resolves invalid ones with explanations, and uses documented product principles to decide ambiguous feedback autonomously.
  • CI Failure Repair: Fixes failing unit and E2E tests, updates snapshots, and ensures all checks pass on the latest PR run.
  • Commit, Push, and Report: Commits and pushes all changes via the pr-push step, then posts a consolidated success or failure summary comment on the PR using the GitHub CLI.
  • Use Case: A reviewer leaves three comments and the lint check fails on your PR. Invoke this Skill to fix the code, push the changes, and post a summary comment without manual intervention.

Quick Start

Fix all outstanding review comments and failing CI checks on the current branch's pull request, then push the changes and post a summary comment.

Frequently Asked Questions about dyad:pr-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix GitHub PR review comments?

Invoke the pr-fix skill with an optional PR number or URL; it defaults to the current branch's PR. It addresses valid review concerns with code changes, resolves invalid ones with explanations, and uses documented product principles for ambiguous feedback.

How to fix failing CI checks on a pull request automatically?

The skill runs a CI-fixing sub-skill that repairs failing unit and E2E tests, updates snapshots when needed, and verifies all checks pass. Afterward it commits, pushes, and posts a summary comment on the PR.

Does this skill work without specifying a PR number?

Yes, the PR number or URL argument is optional. When omitted, the skill targets the pull request associated with the current branch.

What happens if posting the PR summary comment fails?

A failed gh pr comment call, such as from network issues or rate limits, only logs a warning. The skill still reports success if the underlying review and CI fixes completed, since the comment is informational.

When are review comments flagged for human attention?

Comments are flagged only when the documented product principles in rules/product-principles.md do not provide enough guidance to resolve ambiguous or subjective feedback autonomously.