mozilla/firefox-aidev-plugins/nova-cleanup-comments
Claude Code and agent skill by mozilla/firefox-aidev-plugins
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install mozilla/firefox-aidev-plugins/nova-cleanup-commentsSKILL.md
Add Nova Cleanup Comments
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.
Context
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.
Comment Format
Actions
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 logic
Task
- Read the specified file(s) or all modified files if none specified
- Enter plan mode to identify Nova-related changes and propose the set of cleanup comments to add:
- Pref checks for
nova.enabledor similar - Conditionals based on Nova pref
- Files in
Nova/directory - Files in
styles/nova/directory - Import statements choosing between classic/Nova components
- After approval, add the cleanup comments:
- For conditionals:
@nova-cleanup(remove-conditional)with description - For pref checks:
@nova-cleanup(remove-pref)with description - For Nova/ component files:
@nova-cleanup(move-directory)at top of file - For classic component files that have Nova equivalent:
@nova-cleanup(remove-directory)at top - For styles/nova/ files:
@nova-cleanup(merge-styles)at top
- Place comments immediately before the relevant code or at top of file for directory-level actions
- Write descriptions as direct instructions Claude can execute without additional context or engineer guidance
Examples
Notes
- Don't add cleanup comments to pure CSS changes or shared components without conditionals
- If uncertain whether a comment is needed, ask the user
- Multiple cleanup comments in the same file are fine if there are multiple Nova-related changes
- Descriptions must be self-contained — Claude should not need to infer intent or ask follow-up questions to execute them
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/newtab/skills/nova-cleanup-comments/SKILL.md
Popularity
- Repository stars
- 12
- Repository forks
- 16
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/mozilla/firefox-aidev-plugins/nova-cleanup-comments)