pr-fix-comments_skill

This skill reads unresolved PR comments from trusted authors and applies code changes or replies to resolve them efficiently.
  • TypeScript

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-comments

  • SKILL.md10.7 KB

Overview

This skill reads unresolved GitHub PR review comments from a curated list of trusted authors and either addresses, resolves, or flags them for human review. It automates fetching review threads, applying product-principles-guided decisions, making code fixes, replying where needed, and explicitly resolving threads. The skill enforces a strict workflow for traceable task tracking and final PR summarization.

How this skill works

The skill locates the target PR (by argument or current branch), retrieves unresolved review threads via the GitHub GraphQL API, and filters threads to only process those whose first comment author is in the trusted list. For each trusted thread it categorizes the feedback (valid issue, not valid, resolved by product principles, or ambiguous), performs code changes when required, posts explanatory replies when appropriate, and explicitly resolves threads using the GraphQL resolveReviewThread mutation. It tracks progress with TaskCreate/TaskUpdate, runs linting and commits changes, pushes the branch, and posts a top-level PR summary comment.

When to use it

  • You want to automatically address routine suggested fixes from project collaborators and trusted bots.
  • You need consistent application of documented product principles to subjective review comments.
  • You want to reduce manual PR housekeeping (resolving threads, replying to reviewers) for high-trust contributors.
  • You need an auditable summary of which comments were fixed, explained, or flagged for humans.

Best practices

  • Keep the trusted authors list up to date so only intended accounts are auto-processed.
  • Maintain clear, actionable rules in rules/product-principles.md to minimize ambiguous flags.
  • Run the skill on feature branches where commits can be safely amended and pushed.
  • Ensure CI and linting pass locally; the skill runs dyad:lint and requires a clean commit.
  • Verify that replies to 'not valid' comments cite the exact principle number/name when applicable.

Example use cases

  • A collaborator leaves multiple style or bug-fix suggestions across files; the skill applies fixes and resolves threads.
  • A trusted product reviewer leaves a UX trade-off comment that maps to a product principle; the skill enforces the principle and closes the thread.
  • A bot reports minor typing or formatting issues; the skill commits automated corrections and posts the resolution.
  • A comment is unclear or requires further discussion; the skill flags it and leaves a clear, principle-cited request for human attention.

FAQ

Trusted humans and bots are configured in the skill; only comments whose first author matches that list are processed. Other authors are recorded but ignored.

What happens if the product principles don't resolve a judgment call?

The thread is marked ambiguous, a reply is posted citing which principles were considered, and the thread is left open for human review.

Does the skill push code automatically?

Yes — after making changes it runs lint, commits with a standard message including co-author metadata, then invokes the push workflow. Any push errors are reported in the summary.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational