cleanup

Review and fix code against quality gates and security standards.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Objective-Arts/lens --skill cleanup-objective-arts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/Objective-Arts/lens/tree/main/workflow-skills/workflow/cleanup
Command: npx skills add https://github.com/Objective-Arts/lens --skill cleanup-objective-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tsx, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code against established quality standards and security best practices, automatically fixing identified issues to improve code quality and reduce manual review time.

Core Features & Use Cases

  • Comprehensive Code Review: Analyzes code for deterministic violations (secrets, injection) and subjective issues (anti-patterns, design smells).
  • Automated Fixing: Applies necessary changes to resolve identified critical and high-severity findings.
  • Verification: Reruns checks to ensure fixes are correct and no regressions were introduced.
  • Use Case: Before merging a pull request, run /cleanup on the changed files to catch and fix potential security vulnerabilities and code quality issues automatically.

Quick Start

Use the cleanup skill to review and fix issues in the src/auth directory.

Frequently Asked Questions about cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and fix security vulnerabilities before merging?

Automated code review integrates deterministic quality gates with AI-driven subjective analysis to identify and fix security vulnerabilities and code smells. It applies necessary changes to resolve critical findings and then reruns checks to verify the fixes without introducing regressions.

What is the best way to catch anti-patterns and design smells in my source files?

Catching anti-patterns and design smells requires AI-based subjective code review alongside deterministic checks. This approach analyzes code content against established canons and rubrics to detect design flaws, automatically applying fixes to improve overall code quality.

How does automated code fixing handle regression verification?

Automated code fixing handles regression verification by rerunning quality-gate scripts after applying changes. This ensures that the fixes for security vulnerabilities and code smells are correct and do not introduce new issues or break existing functionality.

Do I need specific dependencies to run automated quality gates and code review?

You need the tsx dependency installed to execute the scripts required for automated code review. The process relies on these scripts to run deterministic quality gates for detecting secrets and injection vulnerabilities, alongside AI-driven subjective analysis.

Can I use automated refactoring tools for pre-merge pull request checks?

You can use automated refactoring and review tools for pre-merge pull request checks by running them on changed files. They catch potential security vulnerabilities and code quality issues, automatically applying fixes to ensure the merged code adheres to established quality standards.

When should I avoid using AI-driven code review for fixing code smells?

You should avoid using AI-driven code review when deterministic quality gates alone are insufficient for your specific rubrics, or if your environment lacks the required tsx dependency to execute the necessary verification scripts without causing execution errors.