verify-before-implementing

Inspect filesystem structures and confirm interpretations before implementing changes.

Updated May 1, 2026
One-click install
npx skills add https://github.com/xiaoquqi/hermes-agent-skills --skill verify-before-implementing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-before-implementing
Source: https://github.com/xiaoquqi/hermes-agent-skills/tree/main/productivity/verify-before-implementing
Command: npx skills add https://github.com/xiaoquqi/hermes-agent-skills --skill verify-before-implementing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and align directory structures with explicit user confirmation before implementing changes, preventing misinterpretations of filesystem layouts.

Core Features & Use Cases

  • Inspect and summarize actual filesystem structure: files, directories, and symlinks.
  • Prompt user to confirm interpretation before proceeding, ensuring alignment with expectations.
  • Enforce memory update after user confirmation to preserve decision in context.

Quick Start

Present the discovered file structure and ask the user to confirm whether your interpretation is correct before proceeding.

Frequently Asked Questions about verify-before-implementing

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

FAQPage Schema
How do I verify directory structure before making filesystem changes?

To verify directory structure before filesystem changes, inspect files, directories, and symlinks, then present the layout summary to prompt explicit user confirmation before proceeding with implementation.

What is the best way to prevent incorrect implementations in pipeline configurations?

Preventing incorrect implementations in pipeline configurations requires validating filesystem layouts and aligning directory structures with explicit user confirmation before executing any structural changes.

How do I validate symlinks and path organization before executing data workflows?

Validating symlinks and path organization involves inspecting the actual filesystem structure, summarizing the discovered layout, and requiring user confirmation to ensure alignment with data workflow expectations.

Can I enforce user confirmation before applying filesystem modifications?

Yes, you can enforce user confirmation by presenting the interpreted filesystem structure and requiring explicit approval before executing any directory modifications or updating memory with the decision context.

Why does structure validation matter for pipeline configurations?

Structure validation matters for pipeline configurations because it prevents misinterpretations of filesystem layouts by aligning actual directory paths with expected data workflows before any implementation changes occur.