thermos
/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.
- Author
- michael-denyer ↗
- Repository
- pstack-claude ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Workflow
SKILL.md preview
--- name: thermos description: "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." --- # Thermos On Codex, read the [platform mapping](../poteto-mode/references/codex-tools.md), including its per-skill notes, before following this skill. On GitHub Copilot, read the [platform mapping](../poteto-mode/references/copilot-tools.md), including its per-skill notes, before following this skill. On Muse, read the [platform mapping](../poteto-mode/references/muse-tools.md), 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. 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · michael-denyer/pstack-claude | 90 | MIT |
| chhoumann/t3-pstack | 90 | MIT |
| tommy-ca/pstack | 90 | MIT |
| CMMD-Center/cmmdstack | 90 | MIT |
| maximechbt/skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 022de09b9a64 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90code-review-expert
Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for code-review-expert, double thermo review, or combined bug/security and code-quality branch audits. - 100code-review-expert
Run both thermo-nuclear review (security/correctness) and thermo-nuclear-code-quality-review (maintainability/structure) subagents in parallel, then synthesize findings. Use for full-spectrum branch audits combining bug/security and code-quality passes. The plugin also includes… - 100earth-rumble
Toph's Earth Rumble review. The champion takes on every challenger at once and nothing gets past her. Use to review a diff, a branch, a PR, or a design for correctness bugs, breaking changes, security holes, devex breaks, feature-flag leaks, and maintainability. Runs a… - 90thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use when the user explicitly asks for a thermo-nuclear review, thermonuclear review, deep code quality audit, or an especially harsh maintainability review. Not… - 85thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review. - 100thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.