Cross-reference code, comments, docs, and tests to classify symptoms as bug or intended behavior.
npx skills add https://github.com/emdash-cms/emdash --skill verify-emdash-cms
Please help me install this Agent Skill. Skill: verify Source: https://github.com/emdash-cms/emdash/tree/main/.flue/skills/verify Command: npx skills add https://github.com/emdash-cms/emdash --skill verify-emdash-cms
Diagnose found code that explains the symptom. That does not mean the code is wrong. Plenty of issues filed on EmDash describe behaviour that is intentional but under-documented, surprising at first glance, or a misuse of the API. Your job is to tell the difference, because the fix stage runs only when you say bug.
You read code, comments, docs, tests, and AGENTS.md. You do not modify anything. No source edits, no test runs.
Read the diagnose output, review surrounding code and tests, then decide and document the verdict.
High-intent search queries and answers about installing and using this skill.
To determine if a code symptom is a bug or intended behavior, cross-reference the code with comments, documentation, and tests to identify the original design intent. Reviewing repository guidelines like AGENTS.md helps clarify whether the observed behavior is deliberate.
Diagnosing a reported issue against tests and documentation involves cross-referencing the found code with existing test cases and docs to distinguish intentional design from actual bugs. This process yields a clear verdict of bug, intended-behavior, or unclear.
Yes, code review can check surprising behavior against CONTRIBUTING.md and other repository guidelines to determine intent. Cross-referencing code with these docs helps identify whether the behavior is an undocumented but intentional design choice.
You verify code intent without modifications by reading surrounding code, comments, and tests to build a justification. The process outputs a concise verdict grounded in documentation, strictly avoiding source edits or test execution.
Cross-referencing AGENTS.md helps diagnose code intent because these repository guidelines contain explicit design decisions and behavioral expectations. Comparing code against these guidelines reveals whether a symptom is an intentional design choice or a bug.
When code review returns an unclear verdict on a bug, the investigation lacks sufficient evidence from code, tests, or documentation to confidently determine intent. You should document the unclear status and gather more context before proceeding to any fix stage.
hotriluanValidate UI code against the latest Web Interface Guidelines.
basecampReproduce production bugs and confirm fixes locally via Selenium browser automation.
shynlee04Enforces the RED phase of TDD by requiring a failing test before implementation code.
CaptainPhantasyScan code for getenv calls and flag undocumented environment variables.
