Determines whether diagnosed code behavior is a bug or intended design.
npx skills add https://github.com/Thigh-Food/emdash --skill verify-thigh-food
Please help me install this Agent Skill. Skill: verify Source: https://github.com/Thigh-Food/emdash/tree/main/.flue/skills/verify Command: npx skills add https://github.com/Thigh-Food/emdash --skill verify-thigh-food
bug, intended-behavior, or unclear, each with cited reasoning pointing to specific comments, docs, or tests. - Evidence-based cross-referencing: Reads surrounding code, docstrings, AGENTS.md, CONTRIBUTING.md, docs/, and existing tests to establish documented intent before judging. - Read-only safety: Enforces hard prohibitions on source edits, commits, pushes, and external network calls, so verification never mutates the repository. - Use Case: A reporter claims the API should return a bare array, but the code returns { items, nextCursor }. The Skill finds the pagination contract documented in AGENTS.md, returns intended-behavior, and drafts a comment pointing the reporter to the docs. ## Quick Start Ask the agent to verify whether the diagnosed behavior in the current issue is a bug or intended behavior, citing the relevant docs and tests.High-intent search queries and answers about installing and using this skill.
Cross-reference the diagnosed code against comments, docstrings, AGENTS.md, docs, and existing tests. If the code matches documented intent, it is intended behavior; if it contradicts documented or clearly implied intent and the reporter's expectation is reasonable, it is a bug.
Run a diagnosis to locate the explaining code, then verify intent by reading surrounding code, documentation, and tests. Only proceed to the fix stage when the verdict is bug with high confidence; otherwise post a comment citing the relevant docs.
Not necessarily. A test asserting the current behavior is a strong signal of intent, but a test that asserts wrong behavior is itself part of the bug. Read what the test asserts and why before treating it as proof of intent.
Return an unclear verdict and list what information would be needed to decide. The maintainer then makes the call rather than guessing, avoiding both false fixes and wrongly dismissed reports.
No. Verification is strictly read-only: no source edits, no commits or pushes, no test runs, and no external network calls. It only reads code, docs, and tests to produce a verdict with cited reasoning.
emdash-cmsTrace bug symptoms to the responsible file and approximate line.
emdash-cmsCross-reference code, comments, docs, and tests to classify symptoms as bug or intended behavior.
DonchitosGenerate a complete design or architecture document from your codebase with this intelligent tool.
PREDICTifExecutes implementation plans with verification steps and checkpoint reviews.