npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@first-to-fly/code-cleanup

v1.0.1

Published

MCP for cleaning up code files using Google's Generative AI.

Readme

Code Cleanup MCP Server

A Bun TypeScript project that provides a Model Context Protocol (MCP) server for cleaning up code files using Google's Generative AI. It backs up original files in a .stash directory and allows users to optionally define custom system prompts for the cleanup process.

Features

  • Cleans up code files with a professional software engineering focus (removes unused imports, ensures consistent formatting, etc.).
  • Supports custom system prompts for flexible cleanup instructions.
  • Backs up original files in a .stash directory before modification.
  • Provides tools to manage the stash directory.
  • Built with strong TypeScript typing for reliability.

Installation

For Roo Code

{
  "mcpServers": {
    "code-cleanup": {
      "type": "stdio",
      "timeout": 300,
      "command": "npx",
      "args": ["--yes", "@first-to-fly/code-cleanup"],
      "env": {
        "CODEBASE_PATH": "__PWD__",
        "GOOGLE_API_KEY": "__CODEBASE_GOOGLE_API_KEY__",
        <!-- "SYSTEM_INSTRUCTION": "This is the instruction to clean up the code.", -->
        <!-- "MODEL": "gemini-1.5-pro by default. Feel free to use different one." -->
      },
      "alwaysAllow": ["cleanup_code_files"],
      "disabled": false
    }
  }
}

Default SYSTEM_INSTRUCTION

Clean up the provided code like a professional software engineer, focusing on:

* Removing unused imports, variables, and redundant one line comments (retain only meaningful comment and documentation).
* Ensuring consistent naming and formatting according to language best practices.
* Simplifying minor inefficiencies (e.g., redundant calculations) *without* altering the core logic.
* Removing unnecessary whitespace while preserving single-line breaks between logical blocks of code.

Crucially, *do not* change the code's original logic, variable names (unless obviously incorrect style), or overall functionality.  Do not add any new comments except to clarify existing deprecated code. Do not rewrite or restructure major sections of code.

Output *only* the cleaned, raw code, with proper indentation and formatting.  Do not include any introductory phrases, explanations, annotations, or markdown formatting (backticks or otherwise). The output should be the code itself, ready to be copied and pasted.

Example:

**Not like this:**

\`\`\`javascript
console.log("hello");
\`\`\`

**Like this:**

console.log("hello")

---
Provide back raw code.