verify-against-code

Name: verify-against-code
Availability: InStock
Author: Arx-Game

Inspect codebases to classify surfaces as BUILT, NOT WIRED, or ABSENT.

4|1|Updated Feb 4, 2024

Search Tags:#architecture #code-review #live-caller #anti-reinvention #surface-verification

Ready to run

npx skills add https://github.com/Arx-Game/arxii --skill verify-against-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-against-code
Source: https://github.com/Arx-Game/arxii/tree/main/tools/skills/verify-against-code
Command: npx skills add https://github.com/Arx-Game/arxii --skill verify-against-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before you propose building anything new — or accept that something "doesn't exist" — prove it by reading the code and finding (or failing to find) a live caller. Never let a doc, an index, or a prior summary stand in for that proof.

Core Features & Use Cases

Read the actual code to locate live callers and confirm whether a surface exists
Classify surfaces as [BUILT & WIRED], [BUILT, NOT WIRED], or [ABSENT] to avoid duplicates
Perform capability checks across surfaces to determine if a proposed change is truly new or already achievable

Quick Start

Inspect the codebase to locate a live caller before proposing a new surface.

Frequently Asked Questions about verify-against-code

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

FAQPage Schema

How do I verify if a code surface already exists before proposing new code?▼

To verify code surface existence, inspect the codebase to locate a live caller using grep. Classify surfaces as BUILT & WIRED, BUILT, NOT WIRED, or ABSENT to confirm whether a proposed change is truly new or already achievable.

What is a live caller check in architecture and code review?▼

A live caller check is a surface verification process that reads actual code to locate usages, preventing anti-reinvention by proving a surface exists rather than relying on design specs, stubs, or prior documentation summaries.

How do I prevent building duplicate code surfaces across my codebase?▼

Prevent duplicate code surfaces by performing capability checks across existing surfaces. Use grep to find live usages and classify them as BUILT & WIRED, BUILT, NOT WIRED, or ABSENT before proposing any new architecture changes.

Can I trust design specs and stubs to confirm code existence?▼

You cannot trust design specs or stubs to confirm code existence. You must read the actual code and find a live caller to prove the surface exists, classifying its state to accurately determine if a proposed change is already achievable.

When do I need to perform a capability check before proposing architecture changes?▼

Perform a capability check before proposing architecture changes when you need to determine if a proposed change is truly new or already achievable. Verify code surfaces by locating live callers to prevent anti-reinvention across your codebase.

What is the best way to classify code surfaces during a code review?▼

The best way to classify code surfaces is to grep for live usages and categorize them as BUILT & WIRED, BUILT, NOT WIRED, or ABSENT. This surface verification method ensures you confirm existence before proposing changes.