원클릭으로
dyadfix-issue
Create a plan to fix a GitHub issue, then implement it locally.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Create a plan to fix a GitHub issue, then implement it locally.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | dyad:fix-issue |
| description | Create a plan to fix a GitHub issue, then implement it locally. |
Create a plan to fix a GitHub issue, then implement it locally.
$ARGUMENTS: GitHub issue number or URL.Fetch the GitHub issue:
First, extract the issue number from $ARGUMENTS:
$ARGUMENTS is a number (e.g., 123), use it directly$ARGUMENTS is a URL (e.g., https://github.com/owner/repo/issues/123), extract the issue number from the pathThen fetch the issue:
gh issue view <issue-number> --json title,body,comments,labels,assignees
Sanitize the issue content:
Run the issue body through the sanitization script to remove HTML comments, invisible characters, and other artifacts:
printf '%s' "$ISSUE_BODY" | python3 .claude/skills/fix-issue/scripts/sanitize_issue_markdown.py
This removes:
<!-- ... -->)Analyze the issue:
Explore the codebase:
Determine testing approach:
Consider what kind of testing is appropriate for this change:
Note: Per project guidelines, avoid writing many E2E tests for one feature. Prefer one or two E2E tests with broad coverage. If unsure, ask the user for guidance on testing approach.
IMPORTANT for E2E tests: You MUST run npm run build before running E2E tests. E2E tests run against the built application binary. If you make any changes to application code (anything outside of e2e-tests/), you MUST re-run npm run build before running E2E tests, otherwise you'll be testing the old version.
Create a detailed plan:
Write a plan that includes:
Execute the plan:
If the plan is straightforward with no ambiguities or open questions:
/dyad:pr-push when completeIf the plan has significant complexity, multiple valid approaches, or requires user input:
ExitPlanMode to request approval/dyad:pr-push when complete