michael-denyer/pstack-claude

thermos

Launch both thermo-nuclear review subagents in parallel, then synthesize their findings.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/michael-denyer/pstack-claude --skill thermos

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Thermos

On Codex, read the platform mapping, including its per-skill notes, before following this skill.

On GitHub Copilot, read the platform mapping, including its per-skill notes, before following this skill.

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: "pstack:thermo-nuclear-review-subagent" for bugs, breakages, security, devex regressions, feature-flag leaks, and other branch-audit risks.
  • subagent_type: "pstack:thermo-nuclear-code-quality-review-subagent" for maintainability, structure, file-size growth, spaghetti, abstractions, and codebase-health risks.
  1. Pass each subagent the same scoped diff/file context and ask it to return prioritized findings with file references and evidence.
  2. 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.

Related by task

from this repository

More skills

All skills