inclusion-audit

An inclusion audit analyzes language, internationalization, tone, and mock data to surface who is served and who might be excluded. It checks for default user assumptions, onboarding barriers, and data-handling constraints across a repository.

An inclusion audit is a comprehensive code review process that examines internationalization, tone, and mock data to reveal default user assumptions and potential biases. It identifies onboarding barriers and data-handling constraints that might exclude specific user groups.

You configure inclusion scope by creating a .inclusion-config.md file in your project directory. The audit detects and respects this configuration file to tailor the review scope, priorities, and acknowledged findings before analyzing the target file path or repository.

Yes, you can run an inclusion audit on a specific directory, file path, or entire repository scope. The audit detects internationalization considerations and inclusive language issues while respecting your project's inclusion-config and scope decisions.

An inclusion audit report highlights potential exclusions, default user assumptions, and biases found in code, documentation, and mock data. It provides a structured output detailing language issues, tone analysis, and onboarding barriers based on the configured scope.

Automated bias detection limitations depend on the scope defined in your .inclusion-config.md file. While the audit surfaces potential exclusions and default assumptions in language and data, it requires pre-existing configuration to tailor priorities and acknowledge previously identified findings.