Gotrino Inclusion Plugin
A Claude Code plugin that examines software through an inclusion lens. Ask: Who might this exclude? What assumptions are baked in?
A Claude Code plugin that examines software through an inclusion lens, asking: “Who might this exclude? What assumptions are baked in?”
It functions as a code reviewer focusing on inclusive design rather than a traditional linter.
Background
This plugin grew out of an ethics framework we developed for AI-assisted development. If you’re interested in the thinking behind it, we wrote about the approach on our blog.
If you want to use the framework directly without the full plugin, it’s available as a standalone Gist: Inclusion Framework Gist.
Installation
- Run
/pluginsin Claude Code - Tab to Marketplace
- Enter
hereinthehive/gotrino-inclusion - Choose the scope (user, project, etc.)
- Reload Claude Code
Once installed, run /teach-charter to configure it for your specific project. This creates a .inclusion-config.md file storing your scope decisions, priorities, and acknowledged findings.
Quick Checks
Fast, lightweight commands for everyday use:
/guardian– Lightweight inclusion review of your current code/language-check– Scans for non-inclusive terminology/names-check– Evaluates name diversity in examples and mock data/i18n-check– Identifies internationalization problems
Comprehensive Analysis
Deeper analysis when you need it:
/inclusion-audit– Thorough project-wide review/examples-audit– Examines mock data for cultural biases/test-assumption– Uncovers hidden assumptions about users
Utilities
Helpful tools for building more inclusive software:
/inclusive-names– Generates diverse placeholder names for examples/explain– Creates decision documentation for inclusion choices/impact– Assesses the consequences of changes
What It Examines
The plugin checks for:
- Gendered or ableist language in code and comments
- Western-centric placeholder names (moving beyond “John Smith”)
- Hardcoded dates, currencies, and formats
- Cultural assumptions embedded in test data and examples
- Accessibility considerations beyond automated checkers
Design Philosophy
Unlike a linter that pattern-matches against a blocklist, this plugin emphasizes:
- Contextual judgment – Understanding your specific domain and users
- Explanation over flags – Helping you understand why something might exclude
- Acknowledged findings – Once you’ve addressed or accepted something, it won’t nag
For runtime accessibility testing, we recommend pairing this with dedicated tools like axe-core.
Open Source
This plugin is MIT licensed and open source. Contributions welcome.