skill-logic-conflict-checker-yashu

Conflict detection in skill documentation works by comparing SKILL.md against reference files for literal and semantic contradictions. It evaluates rules for mutual exclusivity, flags mismatched values, and generates a structured report of documentation errors.

Semantic contradiction detection in technical writing evaluates rules for mutual exclusivity, flow logic errors, and broken references. It analyzes underlying meaning across multiple files to identify deep logical inconsistencies in complex project documentation.

Yes, you can validate SKILL.md files against multiple reference documents. The analysis performs comprehensive logical verification across all reference files to find mismatched values, naming inconsistencies, and conflicting constraints before publishing.

Yes, automated quality assurance catches broken references in skill documentation. The conflict detection process evaluates flow logic errors and broken references alongside literal and semantic contradictions to ensure technical guides remain accurate and reliable.

You need to run a documentation consistency check before publishing a complex skill. This prevents user confusion caused by conflicting instructions and verifies that your SKILL.md and all reference documents are perfectly aligned.