fix-terminology

Unify terminological contradictions across editorial units using whole-word replacements.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/JaviMontano/prolipa-plugins --skill fix-terminology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-terminology
Source: https://github.com/JaviMontano/prolipa-plugins/tree/main/scriba/skills/fix-terminology
Command: npx skills add https://github.com/JaviMontano/prolipa-plugins --skill fix-terminology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terminological inconsistencies across editorial units create confusion and hinder comprehension. This skill provides a systematic approach to unify terms and update the glossary, ensuring a single canonical terminology is used throughout the product.

Core Features & Use Cases

  • Synonym drift detection and unification following editorial rules.
  • Polysemy handling by disambiguating terms and creating qualified glossary entries.
  • Substitution mapping with whole-word replacements, glossary updates, and post-change re-audits to ensure consistency across units.
  • Reusable workflow for multi-unit projects, with traceable changes and a formal unification report.

Quick Start

Identify all contradictions, generate a substitution map, apply whole-word replacements, update the glossary, and re-audit for residual conflicts.

Frequently Asked Questions about fix-terminology

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

FAQPage Schema
How do I unify editorial terminology across multiple files?

To unify editorial terminology, load your consistency reports and glossaries to identify contradictions, build a substitution map using whole-word replacements, update the glossary, and re-audit for remaining conflicts. This ensures a single canonical terminology across all units.

What is the best way to handle synonym drift in a glossary?

Handling synonym drift involves detecting contradictory terms across editorial units and applying editorial rules to map them to a single canonical term. The process updates your glossary and applies whole-word replacements to maintain consistency.

How do I resolve polysemy and disambiguate terms in editorial content?

Resolving polysemy requires disambiguating terms that have multiple meanings by creating qualified glossary entries. This clarifies context-specific definitions, ensuring cross-unit consistency when updating editorial content and re-auditing for residual conflicts.

Can I apply terminology unification across multiple editorial units?

Yes, terminology unification applies across multiple editorial units, MinEduc terms, and unit files. It provides a reusable workflow for multi-unit projects that generates traceable changes and a formal unification report for maintaining consistency.

Why do I need to re-audit content after applying a substitution map?

Re-auditing content after applying a substitution map is necessary to detect remaining terminological conflicts. This post-change verification step ensures that whole-word replacements successfully eliminated synonym drift and polysemy across all units.