verify-citations

Verify citations against the codebase and produce a structured report.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/float-ritual-stack/floatty --skill verify-citations-float-ritual-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-citations
Source: https://github.com/float-ritual-stack/floatty/tree/main/.claude/skills/verify-citations
Command: npx skills add https://github.com/float-ritual-stack/floatty --skill verify-citations-float-ritual-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that every assertion in a draft prompt or design memo is backed by actual code in the repository, preventing citation drift.

Core Features & Use Cases

  • Cross-check file paths, line references, and file existence against the real codebase.
  • Validate rule numbers, method signatures, enum values, and API behavior cited in drafts.
  • Produce a structured verification report that classifies verified, missing, wrong, and unverifiable claims for post-review improvements.

Quick Start

Run the verification workflow on a draft to confirm each cited claim against the repository.

Frequently Asked Questions about verify-citations

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

FAQPage Schema
How do I verify claims in a design document against the actual codebase?

Verifying code citations prevents citation drift by ensuring every assertion in your draft prompt or design memo is backed by actual code. It checks file paths, rule numbers, method signatures, enums, and API behavior to confirm documentation matches implementation.

Can I check if file paths and method signatures in my technical draft still exist in the repository?

Yes, you can validate file existence, rule numbers, method signatures, enums, and API behavior by running the verification workflow on your draft. It cross-references these elements against the real codebase to identify missing or wrong claims.

What is the best way to audit a draft for citation drift before final review?

Auditing for citation drift involves applying cross-reference checks to file paths, rule numbers, and method signatures against the actual codebase. This produces a structured verification report classifying claims into verified, missing, wrong, or unverifiable categories for remediation.

What does a codebase verification report include when checking draft citations?

The verification report labels each claim as verified, missing, wrong, or unverifiable. It provides a structured breakdown of file paths, rule numbers, method signatures, enums, and API behavior checks to target remediation where citations diverge from the actual codebase.

How do I cross-reference API behavior and enum values cited in a memo with the actual code?

Cross-referencing API behavior and enums involves validating these cited elements against the actual codebase. The verification workflow checks them alongside file paths and rule numbers, outputting a report that labels each claim as verified, missing, wrong, or unverifiable.

When should I avoid using automated codebase citation verification?

Automated codebase citation verification is not suitable for drafts lacking specific file paths, line numbers, or method signatures. Without concrete repository references to cross-reference, the Skill cannot generate a meaningful structured report classifying verified, missing, or wrong claims.