citation-trail-verification

Verifies structural code premises by direct inspection and records file-and-line citation trails.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill citation-trail-verification-narenkarthikbm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: citation-trail-verification
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/citation-trail-verification
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill citation-trail-verification-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claims about how code behaves — such as "this value enters only through one CLI argument" or "nothing else calls this function" — are often accepted based on a prior document's summary rather than direct evidence. This Skill forces verification against the actual source artifact and produces a durable, re-checkable citation trail instead of an unverifiable "confirmed" marker. ## Core Features & Use Cases - Direct artifact inspection: Identifies the exact source file that confirms or falsifies a premise and inspects it directly, never trusting a prior reviewer's summary or sign-off. - Exhaustive caller and entry-point sweeps: Documents the exact search method (grep pattern, tool invocation, scope) so another reviewer can reproduce the identical result set. - Absence-claim verification: Establishes exclusivity or absence claims through completed, reproducible searches rather than failure to recall a counterexample. - Use Case: A task claims a token aggregate enters token_capture.py only as a CLI argument. The Skill quotes that premise, greps every call site, records file:line citations for each entry point, labels each as directly verified or inherited, and flags anything untraceable as unresolved. ## Quick Start Verify the premise that this value enters the module only through its CLI argument by inspecting the source directly and recording a file-and-line citation trail.

Frequently Asked Questions about citation-trail-verification

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

FAQPage Schema
How do I verify a claim about how a value flows through code?▼

Quote the exact premise first, then inspect the source file that would confirm or falsify it directly. Record a file-and-line citation for every entry point and caller checked, and state the exact search method used so others can reproduce it.

How to prove a function has only one caller or entry point?▼

Run an exhaustive search across the codebase using a stated grep pattern and scope, then show the search returned a singular result. Absence is established by a completed, reproducible search, never by failing to recall a counterexample.

What is the difference between a direct and inherited citation in code review?▼

A direct citation comes from inspecting the source artifact yourself; an inherited citation comes from a prior document's summary or a reviewer's sign-off. Inherited citations must be labeled separately and can never substitute for direct verification of the same claim.

When should citation-trail verification not be used?▼

It is unnecessary for claims that are not load-bearing structural premises, such as style preferences or behavior already covered by failing tests. It targets premises where a wrong assumption would invalidate downstream work.

What happens when an entry point cannot be traced to the claimed source?▼

The untraceable entry point is flagged as unresolved and named specifically, rather than being folded into an overall verdict that the premise holds. The citation trail remains a standalone artifact a future reviewer can re-check.