b-open-io/critique
skills/critique/SKILL.md
This skill should be used when the user asks to "show me the changes", "what did you change", "let me see the diff", "review the code", "open web preview of changes", "show me what you worked on", "compare branches", "explain what changed", or wants to view git diffs in a terminal UI, web browser, or get AI-powered code review explanations.
$ install --global
skillsauthnpx skillsauth add b-open-io/prompts critiqueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 29, 2026, 3:51 AM56.2s4 files scanned
SKILL.md
- name:
- critique
- version:
- 1.0.0
- description:
- This skill should be used when the user asks to "show me the changes", "what did you change", "let me see the diff", "review the code", "open web preview of changes", "show me what you worked on", "compare branches", "explain what changed", or wants to view git diffs in a terminal UI, web browser, or get AI-powered code review explanations.
Review git diffs with syntax highlighting, split view, and word-level diff. Show users what code was changed during a session using terminal UI or web preview.
Prerequisites
Critique requires Bun (does not work with Node.js):
# Run directly (no install needed)
bunx critique
# Or install globally
bun install -g critique
Core Commands
View Current Changes
# Unstaged changes (includes untracked files)
critique
# Staged changes only
critique --staged
# Watch mode - auto-refresh on file changes
critique --watch
View Commits
# Last commit
critique HEAD
# Specific commit
critique --commit HEAD~1
critique --commit abc1234
# Combined changes from last N commits
critique HEAD~3 HEAD
Compare Branches (PR-style)
# What feature-branch added vs main
critique main feature-branch
# What current branch added vs main
critique main HEAD
Filter Files
# Filter by glob pattern
critique --filter "src/**/*.ts"
critique --filter "src/**/*.ts" --filter "lib/**/*.js"
Web Preview
Generate an HTML preview viewable in a browser - ideal for sharing or detailed review:
# Generate web preview
critique --web
# Generate and open in browser
critique --web --open
# Web preview for commits
critique HEAD --web --open
critique main HEAD --web --open
The web preview provides:
- Full syntax highlighting
- Split view with before/after
- Shareable HTML output
- Better for large diffs
AI-Powered Review
Generate AI explanations of code changes. Best for reviewing AI-generated changes:
# Review unstaged changes (uses OpenCode by default)
critique review
# Use Claude Code as the AI backend
critique review --agent claude
# Review specific commits
critique review HEAD
critique review --commit HEAD~1
# Review branch diff (like a PR)
critique review main HEAD
# Include session context for better explanations
critique review --agent claude --session <session-id>
# Generate web preview of AI review
critique review --web
critique review --web --open
AI review features:
- Orders hunks in logical reading order
- Splits large hunks into digestible chunks
- Explains changes with diagrams and tables
- Groups related changes across files
Integrations
Git Difftool
Configure as default git difftool:
git config --global diff.tool critique
git config --global difftool.critique.cmd 'critique difftool "$LOCAL" "$REMOTE"'
Then use: git difftool HEAD~1
Lazygit
Add to ~/.config/lazygit/config.yml:
git:
paging:
pager: critique --stdin
Running from Claude Code
Since the TUI runs inside the Bash tool (hidden/folded), use one of these approaches:
Option 1: Split Pane (macOS with iTerm2, Recommended)
Open critique in a split pane that auto-closes when done:
# Horizontal split (top/bottom)
/path/to/skills/critique/scripts/open-critique-pane.sh /path/to/repo -h
# Vertical split (side by side)
/path/to/skills/critique/scripts/open-critique-pane.sh /path/to/repo -v
Option 2: New Terminal Tab (macOS with iTerm2)
Open critique in a new tab:
/path/to/skills/critique/scripts/open-critique.sh /path/to/repo
Option 3: Web Preview (Cross-platform)
Opens in browser - works everywhere:
bunx critique --web --open
Recommended Usage After Claude Work
When a user asks to see what changed after Claude has made modifications:
- New terminal tab (macOS): Use osascript to open critique in iTerm
- Web preview: Run
critique --web --openfor browser view - AI-explained review: Run
critique review --agent claude --web --open - Compare to starting point: Run
critique HEAD~N HEAD --web --open
Navigation Keys (Terminal UI)
| Key | Action |
|-----|--------|
| j/k or ↓/↑ | Navigate lines |
| h/l or ←/→ | Switch files |
| Tab | Toggle split/unified view |
| q | Quit |
| ? | Help |
Related Skills
b-open-io/claudex
tools
VerifiedTrustedCommunity
This skill should be used when a Claude Code session needs to keep working after Anthropic usage runs out, or when the user asks to run the Claude Code harness on GPT-5.6 Sol. Trigger phrases include "my Anthropic usage ran out", "I'm out of Claude usage", "usage limit reached, what now", "keep working on another model", "run Claude Code on GPT-5.6 Sol", "use GPT-5.6 Sol as the model", "set up claudex", "claudex isn't working", "route the harness through CLIProxyAPI", or "bill against my ChatGPT/Codex subscription". It stands up a local proxy so the Claude Code CLI runs on OpenAI's Codex backend as an escape hatch, and diagnoses that setup when it drifts. macOS + Homebrew.
14SKILL.mdUpdated Jul 17, 2026
b-open-io/visual-wayfinder
testing
VerifiedTrustedCommunity
This skill should be used when the user asks to "open Visual Wayfinder", "answer a Wayfinder ticket visually", "turn this decision into a configurator", "show Wayfinder choices as a dashboard", "prototype the Wayfinder questionnaire", or wants interactive choice cards, tradeoff controls, rankings, ranges, toggles, and consequence previews for one active Wayfinder decision. It wraps the Wayfinder skill and JSON Render; it never replaces the tracker or resolves more than the active decision.
14SKILL.mdUpdated Jul 16, 2026
b-open-io/visual-proposal
development
VerifiedTrustedCommunity
This skill should be used when the user asks to "make a visual proposal", "write this up so I can share it", "present these options visually", "diagram the trade-offs", "turn this plan into something reviewable", or requests a shareable design pitch, architecture proposal, RFC, options comparison, or visual roadmap for work that has not been built. It produces one self-contained, theme-aware HTML page led by grounded diagrams. Use visual-review instead for completed code changes; do not use this skill for internal task tracking.
14SKILL.mdUpdated Jul 16, 2026
b-open-io/plugin-settings
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "add plugin settings", "make a plugin configurable", "store per-project plugin configuration", "use settings.local.json", "create a plugin state file", "expose skill settings in Agent Master", or "add a skill interface". Distinguishes official Claude Code settings from project-owned configuration and documents bOpen Agent Master skill interface discovery.
14SKILL.mdUpdated Jul 16, 2026