dyad:fix-issue

Fetches a GitHub issue, plans a fix, and implements it locally.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Turning a GitHub issue into working code requires manually reading the issue, exploring the codebase, deciding on a testing strategy, and writing the fix. This Skill automates that entire workflow from issue fetch to implementation.

Core Features & Use Cases

  • Issue Fetching and Sanitization: Retrieves issue details via the GitHub CLI and strips HTML comments, invisible Unicode characters, and formatting artifacts that could confuse the AI.
  • Structured Planning: Explores the codebase, identifies files to modify, and produces a plan covering implementation steps, testing approach, and risks.
  • Test Strategy Guidance: Chooses between E2E tests, unit tests, or no tests based on the change type, with a reminder to rebuild before running E2E tests.
  • Use Case: A maintainer receives a bug report as GitHub issue #123. They invoke the Skill with the issue number, and it fetches the issue, analyzes the relevant code, plans the fix, implements it, and pushes a PR.

Quick Start

Fix GitHub issue number 123 by fetching it, planning the changes, and implementing the fix locally.

Frequently Asked Questions about dyad:fix-issue

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

FAQPage Schema
How do I automatically fix a GitHub issue with AI?

Provide the issue number or URL as the argument. The Skill fetches the issue with the GitHub CLI, sanitizes the content, explores the codebase, creates an implementation plan, and applies the fix locally before pushing a PR.

How to sanitize GitHub issue markdown before LLM processing?

Pipe the issue body through the included Python script sanitize_issue_markdown.py. It removes HTML comments, zero-width Unicode characters, control characters, and collapses excessive blank lines while preserving code blocks and links.

Does this Skill require the GitHub CLI?

Yes, it uses the gh command to fetch issue data including title, body, comments, labels, and assignees. You must have the GitHub CLI installed and authenticated for the target repository.

Why do E2E tests fail after making code changes?

E2E tests run against the built application binary, not the source code. You must run npm run build after modifying any application code outside the e2e-tests directory, otherwise the tests execute against the old build.

When should I choose unit tests over E2E tests for a fix?

Use unit tests for pure business logic, utility functions, or isolated components. Reserve E2E tests for user-facing features and complete flows, and limit them to one or two broad-coverage tests per feature.