thermos

Launches two parallel code review subagents and synthesizes their findings into a unified verdict.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/rockcookies/skills --skill thermos-rockcookies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thermos
Source: https://github.com/rockcookies/skills/tree/main/skills/cursor-plugins/thermos
Command: npx skills add https://github.com/rockcookies/skills --skill thermos-rockcookies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a branch for both bugs/security risks and code-quality issues requires two distinct review passes, and running them sequentially is slow while merging their results manually is error-prone. This Skill runs both reviews concurrently as background subagents and produces one deduplicated, prioritized findings report. ## Core Features & Use Cases - Parallel Dual Review: Launches the thermo-nuclear-review-subagent (bugs, security, devex regressions, feature-flag leaks) and the thermo-nuclear-code-quality-review-subagent (maintainability, structure, file-size growth, abstractions) simultaneously as background tasks. - Scoped Diff Analysis: Determines review scope from the user request, PR, current branch, or changed files, and passes the same diff context to both reviewers. - Synthesized Findings: Deduplicates overlapping findings, weights issues flagged by both reviewers more heavily, resolves disagreements, and surfaces a unified verdict. - Use Case: Before merging a feature branch, ask for a thermos review to get a single prioritized list of branch-audit risks and code-health concerns with file references and evidence. ## Quick Start Ask the assistant to run a thermos review on the current branch to audit it for bugs, security issues, and code-quality problems in parallel.

Frequently Asked Questions about thermos

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

FAQPage Schema
How do I run a parallel code review on a branch?▼

Invoke the thermos skill with a review scope such as the current branch, a PR, or specific changed files. It launches both thermo review subagents in the background at once and returns a synthesized, deduplicated findings report.

What is the difference between the two thermo review subagents?▼

The thermo-nuclear-review-subagent audits bugs, breakages, security, devex regressions, and feature-flag leaks. The thermo-nuclear-code-quality-review-subagent focuses on maintainability, structure, file-size growth, abstractions, and codebase health.

What do I need to install before using the thermos skill?▼

You must install the skill and copy the matching agent markdown files into Cursor's user agents directory. The orchestrator delegates by agent name, so without the agent files there is nothing to launch.

How are conflicting findings from the two reviewers resolved?▼

Findings are deduplicated across both reviewers, with overlapping issues weighted more heavily. Disagreements are resolved by the orchestrator's own judgment, and the final output keeps summaries brief with the highest-signal findings first.

When should I not use the thermos combined review?▼

Skip it when you only need one type of review, such as a pure security audit or a pure style check, since it always launches both subagents. In those cases invoke the individual review subagent directly.