Is this based on recognized industry standards?

Yes, the terminology and principles are derived from the Google Developer Style Guide and the Inclusive Naming Initiative.

How does it handle large-scale terminology changes?

For large scopes, the skill advises creating separate issues for terminology updates to avoid mixing logic changes with sweeping text replacements, ensuring safer PR reviews.

What terms does the Inclusive Language skill help replace?

It targets non-inclusive terms including master/slave, whitelist/blacklist, gendered language like 'man hours,' and ability-related terms like 'sanity check' or 'blind check.'

Does it automatically rename public API endpoints?

The skill suggests a transition approach, such as adding deprecated aliases for the old terms, to ensure you don't break downstream integrations during the migration.

Can this skill be used for non-code files?

Yes, it is designed to scan and update Markdown documentation, commit messages, and even suggested branch names to ensure consistency across the entire project.

Inclusive Language Standards

Name: Inclusive Language Standards
Author: troykelly

bytroykelly

Herramientas para Desarrolladores

Enforces respectful, accessible, and non-biased terminology across codebases, documentation, and git metadata.

Acerca de

The Inclusive Language skill empowers Claude to automatically identify and replace non-inclusive terminology in your software projects. By adhering to modern industry standards—such as replacing legacy 'master/slave' architecture terms with 'primary/replica' and 'whitelist' with 'allowlist'—it ensures that codebases remain welcoming, professional, and accessible. It provides comprehensive guidance for renaming variables, updating documentation, and managing API deprecations, helping teams foster a more inclusive technical environment while maintaining technical clarity.

Características Principales

Structured migration strategies for public APIs using deprecation aliases and versioning
Alignment with industry-standard guidelines from Google and the Inclusive Naming Initiative
Automated replacement of biased terms like 'master/slave' and 'whitelist/blacklist' with modern alternatives
Comprehensive scanning of documentation and comments for gendered or ability-related language
Validation of git commit messages and branch names against inclusive naming conventions
0 GitHub stars

Casos de Uso

Ensuring technical documentation uses neutral, person-first, and accessible language
Modernizing legacy codebases to meet modern DEI (Diversity, Equity, and Inclusion) standards
Automating style reviews to prevent non-inclusive terms from being merged into production

Acerca de

Características Principales

Structured migration strategies for public APIs using deprecation aliases and versioning
Alignment with industry-standard guidelines from Google and the Inclusive Naming Initiative
Automated replacement of biased terms like 'master/slave' and 'whitelist/blacklist' with modern alternatives
Comprehensive scanning of documentation and comments for gendered or ability-related language
Validation of git commit messages and branch names against inclusive naming conventions
0 GitHub stars

Casos de Uso

Ensuring technical documentation uses neutral, person-first, and accessible language
Modernizing legacy codebases to meet modern DEI (Diversity, Equity, and Inclusion) standards
Automating style reviews to prevent non-inclusive terms from being merged into production