rule-boy-scout

Automate fixing TypeScript errors and lint warnings in touched files.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/FelipePepe/TeamHub --skill rule-boy-scout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-boy-scout
Source: https://github.com/FelipePepe/TeamHub/tree/main/.agents/skills/rule-boy-scout
Command: npx skills add https://github.com/FelipePepe/TeamHub --skill rule-boy-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces the Boy Scout Rule: leave the code cleaner by automatically fixing existing TypeScript errors, lint warnings, and VS Code diagnostics in every touched file.

Core Features & Use Cases

  • Automatically detect and repair active TypeScript errors and lint warnings across modified files.
  • Ensure no new issues are introduced during code generation, edits, or refactors.
  • Suitable for local development and pre-commit checks to maintain code quality across the project.

Quick Start

Before generating or modifying code, run the cleanup protocol to fix TypeScript errors, lint warnings, and VS Code problems in all touched files.

Frequently Asked Questions about rule-boy-scout

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

FAQPage Schema
How do I automatically fix TypeScript errors and lint warnings in modified files?

Automatically fix TypeScript errors and lint warnings in modified files by running a cleanup protocol that enforces the Boy Scout Rule, detecting and repairing active issues across all touched files to ensure zero regressions.

What is the Boy Scout Rule in software engineering?

The Boy Scout Rule in software engineering is the practice of leaving code cleaner than you found it. This approach automatically resolves existing TypeScript errors, lint warnings, and VS Code diagnostics in every touched file during generation or modification.

Can I use VS Code diagnostics to prevent new issues during code generation?

Yes, you can use VS Code diagnostics integration to prevent new issues during code generation. The cleanup protocol detects active diagnostics and guarantees zero regression in errors on touched files across frontend and backend TypeScript projects.

Does this cleanup protocol work for pre-commit checks in continuous integration?

Yes, the cleanup protocol works for pre-commit checks in continuous integration. It is suitable for local development and CI environments to maintain code quality by ensuring no new TypeScript or ESLint issues are introduced during refactors.

Do I need ESLint and the TypeScript compiler to enforce code cleanliness?

Yes, you need ESLint and the TypeScript compiler integrated with VS Code diagnostics to enforce code cleanliness. This combination detects and repairs active errors and lint warnings while guaranteeing zero regression in touched files.