language-check

To analyze code for non-inclusive language contextually, provide a project path to scan codebases, documentation, and user-facing strings. The tool surfaces findings with rationale and avoids blanket changes by respecting existing configurations.

Context-aware inclusive language analysis works by scanning code, comments, and documentation to identify non-inclusive terms based on surrounding intent. It provides contextual, actionable recommendations that fit the project's style rather than flagging terms in isolation.

Yes, you can configure inclusive language checks by using an .inclusion-config.md file. The analysis respects this configuration, skips acknowledged findings, and honors team priorities to ensure safe, contextual recommendations across repositories.

Yes, inclusive language analysis works with user-facing strings and configuration files across repositories. It scans codebases, documentation, and examples to surface non-inclusive language while applying contextual understanding to the findings.

The best way to review code for inclusive language before a release is to run a lightweight contextual analysis on your project path. This surfaces non-inclusive language issues with context, making it suitable for quick checks during development or pre-release reviews.

A limitation of automated inclusive language analysis is that it relies on contextual understanding to avoid blanket changes, meaning it must respect existing .inclusion-config.md files. It provides thoughtful suggestions but requires team configuration to properly skip acknowledged findings.