language-check

Language Check

Analyze files for non-inclusive language, with emphasis on understanding context before flagging issues.

Philosophy

This is not a linter. A linter finds strings; this skill understands code.

The goal is to:

1. Understand what the code/content is doing
2. Consider who will read or use it
3. Identify language that could exclude or harm
4. Provide contextual, thoughtful suggestions

Pattern matching helps find candidates, but your job is to analyze and reason.

Scope

The user may specify a file path, glob pattern, or directory. If not specified, ask what they'd like to check.

Config Integration

Before starting, follow the migration preflight in references/config-migration.md, then read .assistant-config.md from the project root.

If it exists:

1. Read scope decisions and acknowledged findings
2. Skip any acknowledged findings (note them in output)
3. Respect priority settings
4. Note at the top of output: "Config loaded: .assistant-config.md"

If config says certain checks are out of scope, still run language checks (core dignity principles), but respect acknowledged individual findings.

Process

1. Read and Understand

First, read the files to understand:

• What is this code/content for?
• Who is the audience? (developers? end users? both?)
• What's the tone and style?

2. Analyze Holistically

As you read, look for language issues in context:

Gendered language - Does this assume gender? Use "guys", "he/she", gendered job titles?

• Consider: Who reads this? How might non-male or non-binary people feel?

Ableist language - Does this use disability as metaphor? ("crazy", "blind to", "lame")

• Consider: How does this land for someone with that condition?

Racially loaded terms - Does this use terms with harmful history? ("whitelist", "master/slave")

• Consider: What's the impact of normalizing these metaphors?

Dismissive language - Does this assume things are "easy" or "obvious"?

• Consider: Easy for whom? What if someone struggles with this?