second-opinion
Run an external LLM code review with Codex CLI, Gemini CLI, or both. Use when the user asks for a second opinion, external review, Codex review, Gemini review, or wants a model-vs-model review of current changes, a branch diff, a specific commit, or a GitHub pull request.
What this skill does
# Second Opinion Run an independent code review without changing the repo. ## When to use it - non-trivial code changes - risky refactors - security, performance, or concurrency-sensitive edits - schema or API changes - before opening or merging a PR - when the user explicitly wants another model's view ## When to skip it - docs-only or formatting-only changes, unless the user still wants it - repos or diffs that must not be sent to external services - empty diffs If repository guidance or user instructions forbid sending code to third-party tools, stop and ask before proceeding. ## Infer the request first Infer as much as possible from the user's message: - tool: `codex`, `gemini`, or `both` - scope: `uncommitted`, `branch diff`, `commit`, or `PR` - focus: `general`, `security`, `performance`, `error handling`, `architecture`, or a custom concern Ask one concise follow-up only if a missing detail blocks the run. ## Read only what you need - Read [references/workflow.md](references/workflow.md) for scope detection, diff sizing, review-brief construction, and synthesis rules. - Read [references/codex.md](references/codex.md) only if running Codex. - Read [references/gemini.md](references/gemini.md) only if running Gemini. ## Core workflow 1. Detect the scope and compute diff stats. 2. Stop on empty diffs. 3. Warn on large diffs and suggest narrowing scope before spending tokens. 4. Build a short review brief that tells the reviewer: - what changed - what to focus on - how to inspect the diff locally - that the review is read-only - what output format to return 5. Run the selected tool or tools in parallel if independent. 6. Present findings first, then agreement and disagreement across tools. 7. Never auto-apply suggested fixes unless the user explicitly asks. ## Safety defaults - Keep the review read-only. - Do not commit, push, stage, or edit files as part of the second opinion run. - Prefer tool-native review commands over manual diff pasting when the tool can inspect the repo directly. - Prefer prompt files or stdin over fragile one-line shell quoting for long review briefs. - Use explicit timeouts and capture output cleanly when automating external review CLIs. - Clean up temporary prompt and output files after reading them. ## Review result format Present results in this order: 1. Findings by tool, highest severity first. 2. Explicit `No findings` if a tool returns nothing substantive. 3. A short synthesis: - where the tools agree - where they disagree - what looks worth acting on first Keep the synthesis separate from the raw reviewer output so the user can distinguish the outside opinion from your judgment.
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.