boolean-naming

Community

Write clear, unambiguous boolean code.

Authoroborchers
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill addresses the common problem of poorly named boolean variables and functions, which leads to confusion, bugs, and decreased code readability. It enforces clear, question-based naming conventions for booleans.

Core Features & Use Cases

  • Enforces Question-Based Naming: Ensures all boolean identifiers read as a yes/no question.
  • Mandates Prefixes: Requires standard prefixes like is, has, can, should for clarity.
  • Promotes Positive Naming: Guides developers to use positive names and negate in logic, avoiding double negatives.
  • Use Case: When reviewing code, use this Skill to identify and correct ambiguous boolean names like flag, status, or active to more descriptive and unambiguous names like isFeatureEnabled or hasPermission.

Quick Start

Review the current file for any boolean naming issues.

Dependency Matrix

Required Modules

None required

Components

scriptsreferences

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: boolean-naming
Download link: https://github.com/oborchers/fractional-cto/archive/main.zip#boolean-naming

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.