test-assumption

Analyze code to surface hidden user assumptions and generate a structured inclusion report.

5|Updated Jan 14, 2026

Search Tags:#usability #review #assumptions #code-analysis #bias-detection #inclusion

Ready to run

npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill test-assumption

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-assumption
Source: https://github.com/hereinthehive/gotrino-inclusion/tree/main/skills/test-assumption
Command: npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill test-assumption

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface hidden assumptions about users in code to prevent exclusion or harm, helping teams design more inclusive software.

Core Features & Use Cases

Analyze code to surface assumptions across ability, identity, circumstance, and experience.
Respect existing scope and decisions from .inclusion-config.md and generate a structured, prioritized report.
Produce a clear decision record and actionable recommendations for design and implementation.

Quick Start

Run a targeted analysis on a project path to surface user assumptions and generate an inclusion-focused report.

Frequently Asked Questions about test-assumption

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify hidden user assumptions in my codebase?▼

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.

What are hidden usability assumptions and how do they cause exclusion in software?▼

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.

Can I use a .inclusion-config.md file to tailor bias detection results?▼

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.

What is the best way to scan a project directory for potential user harm and bias?▼

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.

Does code analysis for inclusion require any specific dependencies or components?▼

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.