メニュー
Use after tests pass on a Nova feature — before linting or formatting — to annotate changed files with @nova-cleanup instructions for post-launch automated cleanup.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review and authoring guidance for new/changed tests in the Fenix TAE efficiency framework (mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/ui/efficiency). Use when reviewing a diff, PR, or Phabricator revision that adds or modifies files under that path — page objects, selectors, navigation edges, or test files. Also use when authoring a new test and self-checking before submission, when asked to check a test against TAE conventions, classify a test (presence/interaction/behavior), or judge whether a helper belongs in a page object vs. BasePage. Applies the framework's principles and anti-patterns as a review rubric with severity tiers.
End-to-end New Tab train-hop targeting for the Experimenter repo. From a single trainhop version string, files the GitHub targeting issue, branches, adds the NimbusTargetingConfig entry, lints, and stages a drafted commit. Use for "newtab trainhop targeting" requests.
Durable review guidance for Firefox's built-in IP Protection (VPN) module, covering panel UI, proxy/channel filtering, authentication, telemetry, and localization.
| name | nova-cleanup-comments |
| description | Use after tests pass on a Nova feature — before linting or formatting — to annotate changed files with @nova-cleanup instructions for post-launch automated cleanup. |
| allowed-tools | ["Read","Edit","Grep","Glob"] |
Do not add cleanup comments if the user says "skip cleanup comments".
Add @nova-cleanup comments to Firefox newtab code following Project Nova implementation strategy.
Project Nova uses a parallel development approach where classic newtab stays untouched and Nova changes live in isolated directories/conditionals. Cleanup comments serve as instructions for a future automated pass: when Nova ships, Claude will find all @nova-cleanup markers and execute the described cleanup autonomously. Write descriptions as direct, unambiguous instructions that Claude can act on without engineer input.
// @nova-cleanup(action): Instruction for Claude to execute during cleanup
remove-directory - Delete entire classic directorymove-directory - Move Nova/ up one levelmerge-styles - Move styles from nova/ to component locationsremove-pref - Remove pref checkremove-conditional - Remove conditional logicnova.enabled or similarNova/ directorystyles/nova/ directory@nova-cleanup(remove-conditional) with description@nova-cleanup(remove-pref) with description@nova-cleanup(move-directory) at top of file@nova-cleanup(remove-directory) at top@nova-cleanup(merge-styles) at top// Entry point with component selection
// @nova-cleanup(remove-pref): Delete this line; replace Base with NovaBase everywhere in this file
const Base = prefs["browser.nova.enabled"] ? NovaBase : ClassicBase;
// Nova/Base/Base.jsx
// @nova-cleanup(move-directory): Move this file to components/Base/Base.jsx and update all imports
export class Base extends React.Component {
// ...
}