expect vs fix-issue

Two Engineering Claude Code skills, side by side. Pick the right skill for your workflow with a side-by-side look at metadata, sample code, and install commands.

Side-by-side

Tag overlap

Sample code from each SKILL.md

/ork:expect                              # Auto-detect changes, test affected pages
/ork:expect -m "test the checkout flow"  # Specific instruction
/ork:expect --flow login                 # Replay a saved test flow
/ork:expect --target branch              # Test all changes on current branch vs main
/ork:expect -y                           # Skip plan review, run immediately

/ork:fix-issue 123
/ork:fix-issue 456

When to choose each

expect — Diff-aware AI browser testing — analyzes git changes, generates targeted test plans, and executes them via agent-browser (Rust daemon + CDP, ARIA-tree-first). Reads git diff to determine what changed, maps changes to…

fix-issue — Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates…

Both are free to install. If you're unsure, install both — Claude Code skills are isolated by filename and only collide if their trigger phrases overlap (rare). The richest signal is the SKILL.md body itself — open both skill pages and read the first paragraph of each.

Other comparisons in this category

• expect vs scope-appropriate-architecture
• ai-ui-generation vs expect
• ai-ui-generation vs scope-appropriate-architecture
• expect vs python-backend
• expect vs testing-e2e
• python-backend vs scope-appropriate-architecture

See all Claude Code skill comparisons · Browse all Engineering skills · Top 100