Skip to content

thermos

Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.

2,145
installs
0 up / 0 down, score 0.00
votes
13,528
repo stars
Updated
less than a month ago
In the catalog since
1 Oct 2026
From
cursor/plugins
AI & Agents
Get it through your agent npx skills add cursor/plugins@thermos

Skill instructions

Rendered from the published SKILL.md, 16 lines.

Thermos

Run the two thermo review passes as async background subagents in parallel, then synthesize their results.

Workflow

  1. Determine the review scope from the user request, PR, current branch, or relevant changed files.
  2. Gather the diff and any file/context excerpts needed for reviewers to evaluate the change without guessing.
  3. Launch both subagents in the same message with run_in_background: true:
    • subagent_type: "thermo-nuclear-review-subagent" for bugs, breakages, security, devex regressions, feature-flag leaks, and other branch-audit risks.
    • subagent_type: "thermo-nuclear-code-quality-review-subagent" for maintainability, structure, file-size growth, spaghetti, abstractions, and codebase-health risks.
  4. Pass each subagent the same scoped diff/file context and ask it to return prioritized findings with file references and evidence.
  5. After both finish, synthesize the results with findings first, deduplicated across reviewers. Weight overlapping findings more heavily, resolve disagreements with your own judgment, and keep summaries brief.

If individual background summaries are already visible to the user, do not restate them wholesale. Surface the unified verdict, the highest-signal findings, and any remaining uncertainty.