// Bug fix workflow that proves test validity with a red-then-green CI sequence. Commits a failing test first (CI red), then the minimal fix (CI green). Use when fixing a bug, writing a regression test, or when asked to prove a fix works.
Manages cherry-pick backports across stable release branches. Discovers candidates from Slack/git, analyzes dependencies, resolves conflicts via worktree, and logs results. Use when asked to backport, cherry-pick to stable, manage release branches, do stable branch maintenance, or run a backport session.
add, update, or remove a model page entry on the comfy org website. creates a PR to Comfy-Org/ComfyUI_frontend apps/website folder with the change and posts a Vercel preview link back to Slack.
Writes Playwright e2e tests for ComfyUI_frontend. Use when creating, modifying, or debugging browser tests. Triggers on: playwright, e2e test, browser test, spec file.
Use when reviewing Vitest unit-test diffs in ComfyUI_frontend, especially new mocks, store tests, component tests, or bugfix regression tests.
Ships performance fixes with CI-proven improvement using stacked PRs. PR1 adds a @perf test (establishes baseline on main), PR2 adds the fix (CI shows delta). Use when implementing a perf optimization and wanting to prove it in CI.
Diagnoses and fixes flaky Playwright e2e tests by replacing race-prone patterns with retry-safe alternatives. Use when triaging CI flakes, hardening spec files, fixing timing races, or asked to stabilize browser tests. Triggers on: flaky, flake, harden, stabilize, race condition in e2e, intermittent failure.
| name | red-green-fix |
| description | Bug fix workflow that proves test validity with a red-then-green CI sequence. Commits a failing test first (CI red), then the minimal fix (CI green). Use when fixing a bug, writing a regression test, or when asked to prove a fix works. |
Fixes bugs as two commits so CI automatically proves the test catches the bug.
If you commit the test and fix together, the test always passes — reviewers cannot tell whether the test actually detects the bug or is a no-op. Splitting into two commits creates a verifiable CI trail:
The red-then-green sequence in the commit history proves the test is valid.
The user provides a bug description as an argument. If no description is given, ask the user to describe the bug before proceeding.
Bug description: $ARGUMENTS
Create an isolated branch from main:
git fetch origin main
git checkout -b fix/<bug-name> origin/main
Write a test that reproduces the bug. Do NOT write any fix code.
| Bug type | Framework | File location |
|---|---|---|
| Logic, utils, stores, composables | Vitest | src/**/*.test.ts (colocated) |
| UI interaction, canvas, workflows | Playwright | browser_tests/tests/*.spec.ts |
For Playwright tests, follow the /writing-playwright-tests skill for patterns, fixtures, and tags.
reference/testing-anti-patterns.md// src/utils/pathUtil.test.ts
import { describe, expect, it } from 'vitest'
import { resolveModelPath } from './pathUtil'
describe('resolveModelPath', () => {
it('handles absolute paths from folder_paths API', () => {
const result = resolveModelPath(
'/absolute/models',
'/absolute/models/checkpoints'
)
expect(result).toBe('/absolute/models/checkpoints')
})
})
import {
comfyPageFixture as test,
comfyExpect as expect
} from '../fixtures/ComfyPage'
test.describe('Model Download', { tag: ['@smoke'] }, () => {
test('downloads model when path is absolute', async ({ comfyPage }) => {
await comfyPage.workflow.loadWorkflow('missing-model')
const downloadBtn = comfyPage.page.getByTestId('download-model-button')
await downloadBtn.click()
await expect(comfyPage.page.getByText('Download complete')).toBeVisible()
})
})
Run the test locally before pushing to confirm it fails for the right reason:
# Vitest
pnpm test:unit <test-file>
# Playwright
pnpm test:browser:local -- --grep "<test name>"
If the test passes locally, it does not reproduce the bug — revisit your test before pushing.
pnpm typecheck
pnpm lint
pnpm format:check
git add <test-files-only>
git commit -m "test: add failing test for <concise bug description>"
git push -u origin HEAD
gh run list --branch $(git branch --show-current) --limit 1
STOP HERE. Inform the user of the CI status and wait for confirmation before proceeding to Step 2.
Write the minimum code change needed to make the failing test pass.
pnpm typecheck
pnpm lint
pnpm format
git add <fix-files-only>
git commit -m "fix: <concise bug description>"
git push
gh run list --branch $(git branch --show-current) --limit 1
gh pr create --title "fix: <description>" --body "$(cat <<'EOF'
## Summary
<Brief explanation of the bug and root cause>
- Fixes #<issue-number>
## Red-Green Verification
| Commit | CI Status | Purpose |
|--------|-----------|---------|
| `test: ...` | :red_circle: Red | Proves the test catches the bug |
| `fix: ...` | :green_circle: Green | Proves the fix resolves the bug |
## Test Plan
- [ ] CI red on test-only commit
- [ ] CI green on fix commit
- [ ] Added/updated E2E regression under `browser_tests/` or explained why not applicable
- [ ] Manual verification (if applicable)
EOF
)"
Lint, typecheck, or other tests may fail — not just your new test. Check the CI logs carefully. If the failure is unrelated, fix it in a separate commit before the test: commit so the red X is clearly attributable to your test.
The bug may only manifest under specific conditions (e.g., Windows paths, external model directories, certain workflow structures). Make sure your test setup matches the actual bug scenario. Check that you're not accidentally testing the happy path.
If your e2e test is intermittent, it doesn't prove anything. Use retrying assertions (toBeVisible, toHaveText) instead of waitForTimeout. See the /writing-playwright-tests skill for anti-patterns.
If main itself is red, branch from the last green commit or fix the pre-existing failure first. A red-green proof is meaningless if the baseline is already red.
| Resource | Path |
|---|---|
| Unit test framework | Vitest (src/**/*.test.ts) |
| E2E test framework | Playwright (browser_tests/tests/*.spec.ts) |
| E2E fixtures | browser_tests/fixtures/ |
| E2E assets | browser_tests/assets/ |
| Playwright skill | .claude/skills/writing-playwright-tests/SKILL.md |
| Unit CI | .github/workflows/ci-tests-unit.yaml |
| E2E CI | .github/workflows/ci-tests-e2e.yaml |
| Lint CI | .github/workflows/ci-lint-format.yaml |
| Testing anti-patterns | reference/testing-anti-patterns.md |
| Related skill | .claude/skills/perf-fix-with-proof/SKILL.md |