analyze-dependencies
Please perform a comprehensive dependency analysis of this codebase:
Use Playwright to visually test your recent UI changes.
How it fires
How this command gets triggered: by you, by Claude, or both.
/visual-testContext preview
What this command does when you run it.
Use Playwright to visually test your recent UI changes.
Use Playwright to visually test your recent UI changes.
If you have the Playwright MCP server configured (via .mcp.json), Claude Code can:
To use: Simply describe what you want to test and Claude Code will use the Playwright MCP server if available.
1. **Identify what to test**
2. **Run visual tests**
3. **Interaction testing**
4. **Accessibility checks**
5. **Cross-browser validation**
Check your project's test scripts and documentation. Common patterns include:
# Examples - adapt to your project's setup: # npm run test:visual # yarn test:e2e # pnpm test:playwright # python -m pytest tests/visual # bundle exec rspec spec/features # ./gradlew test # For Playwright specifically (if using): # npx playwright test --update-snapshots # playwright test --ui
Remember to commit any new or updated snapshot files if the visual changes are intentional!
Give Claude the super powers it deserves with this power user collection of bash scripts and slash commands
Please perform a comprehensive dependency analysis of this codebase:
Please help me document all APIs in this codebase systematically:
Automatically identify and fix CI failures or review feedback on the current PR, then push the fixes.