verify-resource-existence

Verify whether a resource exists before creating duplicates using glob searches and ignore lists.

6|Updated Mar 11, 2026

Search Tags:#codebase #creation #imports #verify #lookup #resource-existence

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill verify-resource-existence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-resource-existence
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/verify-resource-existence
Command: npx skills add https://github.com/open-hax/opencode-skills --skill verify-resource-existence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents creating duplicate or incorrect resources by exhaustively confirming that the target resource does not already exist.

Core Features & Use Cases

Deterministic verification: searches for existing references and exports to determine presence.
Context-aware checks: evaluates workspace configuration and ignore rules to avoid false positives.
Safe creation guidance: instructs whether to reuse, relocate, or proceed with creation only when absent.

Quick Start

Run the verify-resource-existence protocol before creating a new resource to ensure it does not already exist.

Frequently Asked Questions about verify-resource-existence

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

FAQPage Schema

How do I verify a resource exists before creating a new file in my codebase?▼

To verify resource existence before creation, search for existing references and exports using glob patterns, inspect workspace configuration, and review ignore lists to determine if the resource already exists and prevent duplicates.

Why do modules fail to import when I claim the resource exists but cannot be found?▼

Modules fail to import when the target resource is missing or hidden. Verify resource existence by searching with glob, checking workspace configuration, and reviewing ignore lists to locate or confirm the resource before adding new files or packages.

What is the best way to prevent creating duplicate resources when adding missing references?▼

The best way to prevent duplicate resources is to run an exhaustive verification protocol that searches for existing references and exports, evaluates workspace configuration, and checks ignore rules to decide whether to reuse, relocate, or proceed with creation.

When should I not use a resource existence check before creating a new package?▼

You should not skip a resource existence check when adding files or packages due to missing references. Always verify presence first to prevent duplicates, unless you are certain the target resource does not exist in the codebase.

Can I use glob to find existing exports before proceeding with file creation?▼

Yes, you can use glob to search for existing references and exports during resource verification. Combine glob searches with workspace configuration inspection and ignore list review to confirm absence before creating a new resource.