The `columns` before/after comparison primitive and the PR Visual Recap GitHub Action (agent/model env vars, required tokens, sticky comment, informational scope). Use when building a recap, configuring recap CI, or explaining a Visual Recap check or comment.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add BuilderIO/agent-native --skill plan-review-recaps --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Plan Review Recaps?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/builderio-plan-review-recaps)More formats (shields.io, HTML) on the badges page.
---
name: plan-review-recaps
description: >-
The `columns` before/after comparison primitive and the PR Visual Recap GitHub
Action (agent/model env vars, required tokens, sticky comment, informational
scope). Use when building a recap, configuring recap CI, or explaining a
Visual Recap check or comment.
---
# Review Recaps
- `columns` is the generic before/after layout primitive for structured
comparisons. Use it for side-by-side schema, API, prose, and model blocks.
- The PR Visual Recap GitHub Action runs the `visual-recap` skill on each PR via
an LLM coding agent (Claude Code or Codex, chosen with `VISUAL_RECAP_AGENT`;
model and reasoning depth via `VISUAL_RECAP_MODEL` / `VISUAL_RECAP_REASONING`)
when `PLAN_RECAP_TOKEN` and the backend's API key are configured, shows a
non-required `Visual Recap` check while it runs, then posts a sticky comment
with an inline screenshot. The recap is informational and must not imply the
diff has been reviewed.
## Related Skills
- **visual-recap** — how to generate the recap content itself.
- **plan-authoring-flow** — when `/visual-recap` is the right command.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
