verify

Name: verify
Availability: InStock
Author: EmDash

Cross-reference code, comments, docs, and tests to classify symptoms as bug or intended behavior.

11.6k|1.1k|Updated Apr 1, 2026

Search Tags:#documentation #decision #diagnose #code-review #intent #bug #tests

Ready to run

npx skills add https://github.com/emdash-cms/emdash --skill verify-emdash-cms

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Cross-reference code, tests, and documentation to determine intent.
Help maintainers decide when a reported symptom is a bug or intended behavior.
Provide a clear verdict and reasoning for each investigation.

Quick Start

Read the diagnose output, review surrounding code and tests, then decide and document the verdict.

Frequently Asked Questions about verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I determine if a code symptom is a bug or intended behavior?▼

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.

What is the best way to diagnose a reported issue against existing tests and documentation?▼

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.

Can I use code review to check if surprising code behavior is documented in CONTRIBUTING.md?▼

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.

How do I verify code intent without modifying source files or running tests?▼

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.

Why does cross-referencing AGENTS.md help diagnose repository code intent?▼

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.

What should I do when code review returns an unclear verdict on 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.