@thinkscape/pi-thermos

Thermo-nuclear branch review for Pi: deep correctness and security audits, strict maintainability rubrics, and provider-aware subagent orchestration.

Adapted from Cursor's MIT-licensed Thermos plugin.

Installation

pi install npm:@thinkscape/pi-thermos

The package is published as @thinkscape/pi-thermos and is listed in the Pi package catalog.

Thermos orchestrates review work through a Pi subagent provider. Install the provider you use in Pi:

pi install npm:pi-subagents
# or
pi install npm:@gotgenes/pi-subagents
# or
pi install npm:@tintinweb/pi-subagents

Supported providers:

Provider	Package	Tool shape
Nico	pi-subagents	subagent({ tasks, chain, ... })
Gotgenes	@gotgenes/pi-subagents	subagent({ subagent_type, prompt, run_in_background })
Tintinweb	@tintinweb/pi-subagents	Agent({ subagent_type, prompt, run_in_background })

Install agent definitions

After installing the package in Pi, install the matching Thermos agent definitions into your project or user agent directory:

pi-thermos install-agents --scope project --provider auto

auto installs Nico-compatible definitions by default. Select a provider explicitly when your Pi setup uses another subagent package:

pi-thermos install-agents --scope project --provider gotgenes
pi-thermos install-agents --scope user --provider tintinweb

After installation, run Pi and invoke the thermos command with a base ref, PR URL, or file scope.

Architecture

flowchart TB
  subgraph L2["Orchestrator"]
    TH[thermos]
  end

  subgraph L1["Subagents"]
    SNR[thermo-nuclear-review-subagent]
    SNCQ[thermo-nuclear-code-quality-review-subagent]
  end

  DIFF[git diff + file contents]

  subgraph L0["Rubrics"]
    TNR[thermo-nuclear-review]
    TNCQ[thermo-nuclear-code-quality-review]
  end

  TH --> SNR
  TH --> SNCQ
  SNR --> TNR
  SNR --> DIFF
  SNCQ --> TNCQ
  SNCQ --> DIFF

Methodology

Thermos separates two review questions:

• Will this branch break functionality, security, devex, or feature gates?
• Did this branch make the codebase structurally worse?

The Pi package detects the available subagent provider and builds the right payload for that provider. Integration tests use dry-run payload generation and do not require API keys or a running Pi session.

Attribution

This package adapts methodology, diagrams, and prompt structure from Cursor's Thermos plugin. See the repository NOTICE.md for the upstream MIT notice.