What problem does it solve? Claims made in Discord discussions about a project's state often drift from what the repository actually contains, leaving teams unsure whether a feature is done, a decision was implemented, or a bug was fixed. This Skill verifies those claims against concrete repository evidence and reports each one as confirmed, contradicted, or unresolved. ## Core Features & Use Cases - Two-way cross-referencing: Maps Discord claims to supporting, conflicting, implementing, or superseding repository evidence, and checks whether repository changes are still accurately reflected in Discord discussions. - Untrusted-content discipline: Treats all Discord content as quoted evidence rather than instructions, never executing commands, following links, or accepting credentials found in messages. - Gated send operation: Analysis is read-only by default; sending a message to Discord requires explicit intent, pre-approved exact text, an unambiguous destination, and confirmed send capability. - Use Case: A teammate says in Discord that the boss mechanic is finished. Ask the agent to check whether the repository actually proves it, and receive a mapping of the claim to code, tests, and decision records with a confirmed/contradicted/unresolved verdict. ## Quick Start Check whether the Discord claim that the boss mechanic is complete is actually supported by evidence in this repository.
