Code janitor and optimization

VerifiedCaution

Performs deep repository maintenance by analyzing source code, detecting unused functions, and optimizing GCP deployments. Use this skill to clean up the project, remove redundant code, or reduce the cloud footprint.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude Code
#code-cleanup#static-analysis#project-maintenance#gcp-optimization

Recommended for

Our review

Performs deep maintenance on the OlyBars repo by analyzing code for unused functions and optimizing GCP deployments.

Strengths

  • Identifies dead code through static analysis
  • Optimizes Cloud Run configurations on GCP
  • Produces a clear and actionable Hygiene Report
  • Reduces project bloat and complexity

Limitations

  • Only works with the OlyBars repository
  • Requires running a specific script
  • May miss dynamically referenced functions
When to use it

Use this skill when the user asks to optimize or clean up the OlyBars project.

When not to use it

Do not use it if the project is not OlyBars or if broader code quality improvements are needed.

Security analysis

Caution
Quality score72/100

The skill uses a shell command to execute a repository script, which falls under powerful tooling. While the intent is legitimate maintenance, the script’s behavior is unverified, so caution is warranted.

Findings
  • The skill instructs running a locally-provided TypeScript script via npx, which could perform arbitrary file system operations or network requests. Although the script is intended for static analysis and cleanup, without auditing its contents, there is inherent risk in execution.

Examples

Optimize project
Optimize the OlyBars project and clean up any redundant code.
Clean up site
Clean up the site and find any unused functions in the codebase.
Run janitor
Run the janitor script to perform a hygiene check on the repository.

name: janitor description: Performs deep maintenance on the OlyBars repo. Use this when the user asks to "optimize the project," "clean up the site," or "find redundant code."

Janitor Skill

Goals

  • Maintain a lean, high-performance us-west1 GCP footprint.
  • Ensure the repository remains readable for other agents in the swarm.

Instructions

  1. Introspection: Read ARCHITECTURE.md and the package.json to understand the intended stack.
  2. Analysis: Traverse the src/ directory. Use static analysis to find functions with no internal references.
  3. GCP Guardrails: Verify Cloud Run configurations in server/ aren't bundling unnecessary folders (e.g., tests/ or docs/) into the production container.
  4. Propose: Create a "Hygiene Report" artifact with a checklist of suggested deletions.

Execution

Use the custom script scripts/janitor.ts to perform the heavy lifting of static analysis.

npx tsx scripts/janitor.ts
Related skills