Pull requests become stronger with visual proof. You can capture a demo reel using GIFs, terminal recordings, or screenshots. The capture shows real product usage, not test output. Use it when you ship UI changes, CLI features, or any work with observable behavior.
Never record secrets or use fake placeholders. The tool scans for credentials and discards unsafe captures. It detects your project type and suggests the best capture method. Then it uploads the result and gives you markdown for your pull request.
Global
mkdir -p ~/.claude/skills/ce-demo-reelProject
mkdir -p .claude/skills/ce-demo-reelSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues