llm-assist

Spawn external LLM CLIs for code review and debugging workflows.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/wnz99/claude-skills --skill llm-assist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-assist
Source: https://github.com/wnz99/claude-skills/tree/main/skills/llm-assist
Command: npx skills add https://github.com/wnz99/claude-skills --skill llm-assist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you get independent help from another LLM when you need a stronger answer than a single model can provide. It is designed for debugging, code review, planning, verification, root cause analysis, rescue after repeated failures, and direct code questions.

Core Features & Use Cases

  • Cross-model collaboration: Runs Claude, Codex, or OpenCode as an external thinking partner so you can compare perspectives.
  • Safe prompt assembly: Builds prompt files with project instructions, protected quoting, and monitored execution to avoid brittle ad hoc CLI calls.
  • Structured workflows: Supports review, debug, plan, verify, rca, rescue, and ask modes with clear provider selection and output synthesis.
  • Use case: Ask it to review a tricky diff, confirm a fix, or investigate a bug when you want a second opinion before changing code.

Quick Start

Ask the llm-assist skill to run the complementary external LLM on your current code problem and return a synthesized answer.

Frequently Asked Questions about llm-assist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a second opinion from another LLM for code review?

To get a second opinion for code review, you can spawn an external LLM CLI like Claude, Codex, or OpenCode. This cross-model workflow builds safe prompt files with project instructions to compare perspectives on local changes or PRs.

Can I use cross-model workflows to verify a bug fix?

Yes, you can use cross-model workflows to verify a bug fix. Running external LLMs in verify or debug modes confirms rescue attempts and investigates root cause analysis through a monitored, headless execution environment.

What is the best way to debug code when a single model keeps failing?

The best way to debug repeated failures is to trigger a rescue attempt using an external LLM. This approach leverages cross-model collaboration to provide an independent perspective, bypassing the original model's limitations.

Does this approach require specific setup for CLI automation?

Yes, it requires safe prompt-file assembly and project instruction inclusion for headless execution. You must ensure proper provider selection and monitored output to execute the external LLM CLI safely within your environment.

When should I not use an external LLM for root cause analysis?

You should avoid using external LLMs for root cause analysis when your project lacks clear instructions for safe prompt assembly. Without monitored execution and protected quoting, brittle ad hoc CLI calls may produce unreliable outputs.