Skip to content

Cursor plugin specification and official plugins

TypeScript

Scrub internal references from Thermos skills

ericzakariasson5102244dabd6
diff --git a/thermos/skills/thermo-nuclear-code-quality-review/SKILL.md b/thermos/skills/thermo-nuclear-code-quality-review/SKILL.md
index 34780392..ac76a2bc 100644
--- a/thermos/skills/thermo-nuclear-code-quality-review/SKILL.md
+++ b/thermos/skills/thermo-nuclear-code-quality-review/SKILL.md
@@ -10,8 +10,6 @@ Use this skill for an unusually strict review focused on implementation quality,
Above all, this skill should push the reviewer to be **ambitious** about code structure. Do not merely identify local cleanup opportunities. Actively search for "code judo" moves: restructurings that preserve behavior while making the implementation dramatically simpler, smaller, more direct, and more elegant.
-This skill is based on the built-in **Improve code quality** quick action prompt, extends it with explicit code-quality constraints requested by Sualeh, and incorporates high-signal code-quality preferences distilled from the `lukas-pr-review` skill.
-
## Core Prompt
Start from this baseline:
diff --git a/thermos/skills/thermo-nuclear-review/SKILL.md b/thermos/skills/thermo-nuclear-review/SKILL.md
index 16135f94..1aa5dfd0 100644
--- a/thermos/skills/thermo-nuclear-review/SKILL.md
+++ b/thermos/skills/thermo-nuclear-review/SKILL.md
@@ -1,12 +1,12 @@
---
name: thermo-nuclear-review
-description: Run the web "Deep review" branch-audit prompt. Use for thermo nuclear, thermonuclear, or deep review requests, or current-branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
+description: Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
disable-model-invocation: true
---
# Thermo Nuclear Review
-Use this skill to run the exact review posture from the web "Deep review" quick action.
+Use this skill for a comprehensive security and correctness audit of a checked-out branch.
## Prompt
@@ -33,14 +33,14 @@ It can be easy to break developers' ability to run / build the code locally. You
The codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough.
## Intended Breakage Guidelines
-If you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer at Stripe pushes a PR called "Delete the database"), or you are worried that the change is actually malicious, you should still report the finding.
+If you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer pushes a PR titled "Delete the database"), or you are worried that the change is actually malicious, you should still report the finding.
## Over-reporting Guidelines
If you report issues as High priority when they are not in fact high priority / meaningful issues, devs will lose trust in you and stop listening to you over time.
NEVER misreport the priority / importance of issues. Be extremely thorough in tracing issues end-to-end to gain complete, and total confidence before reporting.
# Final Response
-IF you have memdium-to-high priority / risk findings, and there is a PR for this branch, then check the PR/MR discussion using gh/glab cli to see if there are comments from BugBot or others present.
+IF you have medium-to-high priority / risk findings, and there is a PR for this branch, then check the PR/MR discussion using gh/glab cli to see if there are comments from BugBot or others present.
If so, take their findings into account. If they found issues you missed, evaluate them to determine if they are valid and include them in your report. If they found some of the same issues you did, see if there is anything from their findings that are worth incorporating into your response.
Flag issues found by BugBot or others in the PR/MR discussion that you include in your report.