test-assumption

You can identify hidden user assumptions in code by running a targeted analysis on a file path, directory, or glob pattern. The tool returns a structured report detailing identified assumption categories, potential exclusion impacts, and recommended mitigations.

Hidden usability assumptions are unchecked biases about user ability, identity, circumstance, or experience embedded in code. They cause exclusion by failing to accommodate diverse users, which code analysis can surface to help teams design more inclusive software.

Yes, bias detection honors an existing .inclusion-config.md file to tailor findings. This respects your project's existing scope and decisions, ensuring the structured, prioritized report aligns with your specific inclusion goals and constraints.

The best way to scan for user harm and bias is to run an inclusion-focused analysis on your project directory. It generates a structured, prioritized report and a clear decision record with actionable recommendations for design and implementation.

Code analysis for inclusion requires no external dependencies or components. It operates directly on your project paths to surface hidden user assumptions and generate mitigations, making it straightforward to integrate into your existing software engineering workflow.