contradiction-fixer-yashu

To fix logical contradictions in technical documentation, you must identify patch-based writing patterns where authors mask inconsistencies with supplementary notes, then perform root-cause refactoring to resolve the conflicting mechanism descriptions.

Patch-based contradictions occur when supplementary notes are added to mask logical inconsistencies instead of fixing the root cause. This includes limiting patches, terminology redefinitions, and mechanism demotions that create conflicting arguments within the text.

You can detect terminology mismatches and inconsistent arguments in SKILL.md files by scanning the text for five specific types of patch-based contradictions, including terminology redefinitions and mechanism demotions, to ensure documentation integrity.

Your documentation has a logical contradiction because a patch-based note was added to mask an inconsistency. You must perform root-cause refactoring to rewrite the section and eliminate the conflicting mechanism descriptions for clarity.

The best way to refactor documentation for logical consistency is to replace superficial patches with a structured workflow that analyzes text for inconsistent arguments and terminology mismatches, ensuring documentation integrity and clarity through root-cause resolution.

Contradiction analysis for quality assurance is designed for technical documentation and SKILL.md files. It identifies conflicting mechanism descriptions and patch-based writing patterns to facilitate root-cause refactoring, ensuring logical consistency in your writing.