Analyze code examples and mock data for name diversity and biases.
npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill names-check
Please help me install this Agent Skill. Skill: names-check Source: https://github.com/hereinthehive/gotrino-inclusion/tree/main/skills/names-check Command: npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill names-check
Analyze examples and mock data for name diversity, understanding the context and purpose before suggesting changes. Use when reviewing test data, documentation, or seed data.
Run /names-check on a project to assess name diversity in samples and documentation.
High-intent search queries and answers about installing and using this skill.
Name diversity in test data is checked by analyzing code examples and mock data to reveal Western-centric biases. The tool assesses cultural and regional coverage across your codebase to identify gaps in user-facing documentation and seed data.
Name diversity analysis for seed data identifies and evaluates cultural representation within mock data and documentation. It assesses patterns and gaps across your codebase to ensure test data reflects inclusive naming conventions across different regions and cultures.
To ensure mock data includes edge cases like diacritics, apostrophes, long names, and non-Latin scripts, apply a name diversity analysis that counts these instances. The tool identifies missing edge cases and proposes diverse alternatives when needed.
Yes, you can apply context-aware name diversity analysis to user-facing documentation. The tool prioritizes content changes by understanding the context and purpose of the examples before suggesting diverse naming alternatives for your docs.
The best way to find Western-centric naming patterns is to run a comprehensive analysis across your project files. This reveals existing cultural patterns and gaps in your seed data, allowing you to apply context-aware prioritization for diverse alternatives.
qytay-paloRun methodology, accuracy, and bias checks on analytics artifacts.
tejovanthnGenerate structured documentation with YAML frontmatter and standard sections.
TeamSloppyPlan and author focused tests for Swift projects and CI pipelines.
hereinthehiveAnalyze mock data and examples to identify cultural assumptions and inclusivity gaps.
