tighten

Remove boilerplate and noise from working code while preserving behavior.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/nokusukun/sublime --skill tighten
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tighten
Source: https://github.com/nokusukun/sublime/tree/main/tighten
Command: npx skills add https://github.com/nokusukun/sublime --skill tighten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delete-only pass on working code that removes ceremony, redundant guards, empty catches, banner comments, JSDoc that mirrors types, and other noise while leaving behavior identical.

Core Features & Use Cases

  • Remove boilerplate and noise while preserving behavior.
  • Target code with working logic but bloated structure; verify by tests.
  • Use when code works but contains unnecessary ceremony that raises reading tax.

Quick Start

Apply the tighten pass to a target file or folder and verify that tests still pass.

Frequently Asked Questions about tighten

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

FAQPage Schema
How do I remove boilerplate and banner comments without changing code behavior?

To remove boilerplate and noise while preserving behavior, apply a delete-only pass that strips ceremony, redundant guards, and banner comments. This code cleanup approach requires existing tests to validate that deletions do not alter the functional logic.

What is code noise removal and when should I use it on a working codebase?

Code noise removal is a refactoring technique that deletes unnecessary ceremony, empty catches, and JSDoc mirroring types from working code. Use it when code functions correctly but suffers from high reading tax due to bloated structure.

Do I need tests to safely delete boilerplate and redundant guards during a refactor?

Yes, you need tests to safely delete boilerplate and redundant guards. Validating behavior after a code cleanup pass requires a test suite to confirm that removing empty catches and ceremony does not alter the working logic.

What's the best way to clean up JSDoc that just mirrors TypeScript types?

The best way to clean up JSDoc mirroring types is a targeted delete-only pass that removes the redundant documentation while preserving behavior. This noise removal reduces reading tax without altering the underlying code logic.

What are the limitations of a delete-only pass for code cleanup?

A delete-only pass for code cleanup is limited to removing noise like empty guards and banner comments; it cannot fix broken logic or alter behavior. It adheres to strict safety rules, meaning it only applies to codebases that already function correctly.