feedback verify with real data

Stop relying on assumptions, outdated documentation, or hallucinated function signatures. This skill enforces a "verify first" workflow, requiring concrete evidence from the codebase or live API responses before making any claims. It prevents the common pitfall of assuming a feature exists just because it is mentioned in a README or a TODO list.

What it does

• Symbol verification ensures functions, classes, and variables actually exist in the current directory before referencing them.
• API tier probing uses data-driven tests to determine actual service limits rather than relying on HTTP status codes.
• TODO consolidation filters out completed tasks by cross-referencing checklist items against the live codebase.
• Endpoint mapping validates the existence of specific routes using targeted grep patterns on router files.
• Uncertainty handling provides exact commands for the user to run when local tool access is restricted.

How it works

1. Grep codebase for specific function definitions, symbol references, or migration keywords before asserting state.
2. Execute data probes against external APIs by requesting specific data ranges or schemas that differentiate between service tiers.
3. Cross-reference tasks against the existing file structure to identify and drop obsolete TODO items.
4. Cite evidence by providing file paths and line numbers for every claim made about the system.

Frameworks & tools

This skill utilizes standard shell utilities like grep, ls, and bash. It is designed for developers working with REST APIs and multi-directory codebases across backend/, frontend/, and db/migrations/ structures.

Why this beats prompting it yourself

Standard prompts often lead to confident hallucinations based on outdated context or docstrings. This skill mandates a specific verification loop using grep and data-driven probes, ensuring every statement is citable to a specific line of code or a validated API response shape.

Use cases

• Auditing a legacy codebase to find orphaned symbols or missing endpoints.
• Determining if an external API key has exceeded its quota or is restricted to a lower tier.
• Cleaning up stale TODO lists by verifying which features have already been merged.
• Validating the success of a database migration by checking the migration history.

Known limitations

Verification is limited to the files and tools accessible in the current environment. It cannot verify external API behavior without an active network connection or valid API keys.