boy-scout-rule

Make small, safe improvements to every file you touch during code reviews and edits.

6|2|Updated Feb 28, 2026

Search Tags:#refactoring #code-quality #best-practices #pull-request #code-maintenance #incremental-improvement

Ready to run

npx skills add https://github.com/JordanCoin/codingskills --skill boy-scout-rule-jordancoin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: boy-scout-rule
Source: https://github.com/JordanCoin/codingskills/tree/main/skills/boy-scout-rule
Command: npx skills add https://github.com/JordanCoin/codingskills --skill boy-scout-rule-jordancoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Leave every touched file a little better than you found it, reducing creeping debt and keeping codebases healthier over time.

Core Features & Use Cases

Small, safe improvements completed during regular work
Encourages consistent cleanup across edits, reviews, and bug fixes
Useful in PRs and pair programming to steadily improve readability and maintainability

Quick Start

Observe a file you touch, make a tiny, safe improvement (e.g., rename a variable for clarity, remove a dead import, or add a missing type annotation), and commit it separately from new features.

Frequently Asked Questions about boy-scout-rule

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

FAQPage Schema

How do I reduce code debt during regular feature work and bug fixes?▼

Apply the boy-scout rule to make small, safe, scoped improvements on every touched file. Enforce commit discipline with separate cleanup commits and documentation notes to prevent creeping debt during regular feature work and bug fixes.

What is the best way to maintain clean code after changes in a pull request?▼

Maintain clean code by enforcing commit discipline with separate cleanup commits and documentation notes. Observe touched files during reviews, make tiny safe edits like adding missing type annotations, and commit them separately from new features.

How does incremental code maintenance work during hotfixes?▼

Incremental code maintenance works by requiring change-local edits scoped to touched files. You make tiny safe improvements like removing dead imports or renaming variables for clarity, then commit them separately to ensure every hotfix leaves code better.

Can I use incremental improvement techniques for pair programming and code reviews?▼

Yes, incremental improvement applies to pair programming and code reviews. It encourages consistent cleanup across edits, steadily improving readability and maintainability through small, safe, scoped improvements on touched files.

Why should cleanup commits be separated from feature commits?▼

Cleanup commits should be separated to enforce commit discipline during code maintenance. This separation ensures small, safe improvements like renaming variables or adding type annotations are clearly documented, preventing creeping debt and maintaining clean code after changes.