review-package
Create a self-contained review package of current work for external review by another AI model or human reviewer. Bundles relevant files with a contextual README and instructional prompt. Triggers: "review package", "create review package", "hand off for review", "get a second opinion", "external code review", "cross-model review", "package for review", "prepare code review". Accepts an optional focus area argument to scope the analysis.
What this skill does
# Review Package Creator
Bundle current work into a self-contained zip with a contextual README and review prompt, ready to hand off to any external reviewer.
## Phase 1: Gather Requirements
Ask the user two questions using AskUserQuestion:
**Question 1: Review Type**
- Header: "Review type"
- Question: "What type of review do you need?"
- Options:
1. **Code review** — Line-by-line feedback on implementation, bugs, edge cases, best practices
2. **Architecture review** — High-level feedback on patterns, structure, design decisions
3. **Both** — Comprehensive review covering code and architecture
**Question 2: Specific Concerns**
- Header: "Focus areas"
- Question: "Any specific concerns you want the reviewer to address?"
- multiSelect: true
- Options:
1. **General review** — No specific focus, broad feedback welcome
2. **Performance** — Efficiency, optimization opportunities
3. **Security** — Vulnerabilities, input validation, auth patterns
4. **Maintainability** — Code clarity, complexity, future extensibility
Wait for responses before proceeding.
## Phase 2: Analyze Codebase
Spawn the analyzer agent:
- **subagent_type**: `review-package-analyzer`
- **prompt**: Include focus area ($ARGUMENTS or "current work"), review type from Phase 1, and project root (cwd).
Wait for the agent to return its structured analysis.
## Phase 3: Generate README
Generate a unique suffix for temp files (e.g., timestamp: `date +%s`). Use this for all temp paths in subsequent phases.
Read `references/readme-guide.md` for structure guidelines. Write the README to `/tmp/review-readme-{suffix}.md`.
Adapt the README to the project — don't fill in a rigid template mechanically. The guide provides the sections and priorities; use judgment about what to emphasize based on the review type and analysis results.
## Phase 4: Create File List
Extract all file paths from the analysis (Core, Related, Tests, Config). Write one path per line to `/tmp/review-filelist-{suffix}.txt`.
## Phase 5: Create Package
Locate the packaging script:
```bash
find ~/.claude -path "*/review-package/scripts/create-review-zip.sh" -type f 2>/dev/null | head -1
```
Run it:
```bash
/path/to/create-review-zip.sh \
"$(pwd)" \
"/tmp/review-readme-{suffix}.md" \
"/tmp/review-filelist-{suffix}.txt" \
"review-package-$(date +%Y%m%d-%H%M%S)"
```
## Phase 6: Generate Instructional Prompt
Read `references/prompt-guide.md` for the template. Customize based on review type, focus areas, and concerns from the analysis.
Write to `/tmp/review-prompt-{suffix}.md` and copy to clipboard:
```bash
cat /tmp/review-prompt-{suffix}.md | pbcopy
```
## Phase 7: Report
Tell the user: zip location, file counts (core/related/tests), display the instructional prompt inline, and list next steps (open a new chat with any AI model, paste prompt, upload zip). Mention the prompt is on the clipboard and saved to the temp path.
Clean up temp files (keep the prompt file):
```bash
rm -f /tmp/review-readme-{suffix}.md /tmp/review-filelist-{suffix}.txt
```
## Notes
- If $ARGUMENTS is empty, the analyzer auto-detects current work from git status and recent changes
- For non-git projects, the analyzer falls back to recently-modified files
- The package is self-contained — the reviewer needs no other context
- Files are copied with directory structure preserved
- Binary files and build artifacts are excluded automatically
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.