repo-claim-verifier

Verify repository analysis claims against source code and architecture graphs.

1|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/Emeryzlol/repo_scanner --skill repo-claim-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-claim-verifier
Source: https://github.com/Emeryzlol/repo_scanner/tree/main/.claude/skills/repo-claim-verifier
Command: npx skills add https://github.com/Emeryzlol/repo_scanner --skill repo-claim-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inaccurate repository analysis by systematically verifying architectural claims against source code, component relationships, and external evidence instead of relying on assumptions.

Core Features & Use Cases

  • Code-First Claim Verification: Checks inferred and speculative repository claims through targeted grep analysis while avoiding unnecessary file reads and repository re-cloning.
  • Architecture Graph Validation: Uses DFS-based relationship checks to confirm or correct component connections, boundaries, and security flows.
  • Evidence-Based Reporting: Produces confidence classifications and revision guidance for repository analysis reports, useful for security reviews and technical documentation.

Quick Start

Use the repo-claim-verifier skill to validate the claims in the provided repository analysis packet and generate a verification report.

Frequently Asked Questions about repo-claim-verifier

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

FAQPage Schema
How do I verify repository analysis claims against actual source code?

You can verify repository claims by applying targeted code searches and graph relationship checks against the source code. This validation process uses structured verification packets to confirm architectural connections and security flows without re-cloning the repository.

What is graph-based architecture validation for GitHub repositories?

Architecture graph validation uses DFS-based relationship checks to confirm or correct component connections, boundaries, and security flows. It systematically validates architectural relationships within a repository to ensure inferred technical claims match the actual codebase structure.

How do I validate security assessment claims without re-reading entire repository files?

Security assessment claims can be validated using targeted grep analysis that checks specific assertions against source code evidence. This approach avoids unnecessary file reads by focusing searches directly on the claims requiring verification within the structured packet.

Can I use this for technical claim validation on any GitHub repository?

Technical claim validation applies to GitHub repository reviews, security assessments, and architecture documentation. It requires structured verification packets containing the claims to check, and uses controlled web validation for any claims left unresolved by the source code searches.

What are the limitations of automated code verification for architectural claims?

Automated code verification relies on structured verification packets and targeted searches, meaning claims outside the provided packet or unresolved by source code require controlled web validation. It cannot verify claims lacking sufficient code evidence or architectural graph relationships.