command-verify

Verify documented commands in Markdown files using git-diff caching.

1|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/d-oit/command-verify --skill command-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-verify
Source: https://github.com/d-oit/command-verify/tree/main/.claude/skills/command-verify
Command: npx skills add https://github.com/d-oit/command-verify --skill command-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm.

What problem does it solve?

This Skill eliminates the tedious, error-prone manual checking of commands in documentation. It ensures that all instructions, code snippets, and examples in your markdown files are accurate and up-to-date, preventing users from encountering broken commands. By leveraging intelligent caching, it achieves this with zero token cost after the initial setup, saving significant time and resources.

Core Features & Use Cases

  • Intelligent Caching: Uses Git diff to identify changed files and only revalidates affected commands, ensuring rapid, efficient checks.
  • Command Categorization: Automatically classifies commands as Safe (auto-execute), Conditional (requires confirmation), or Dangerous (never auto-execute), enhancing security and control.
  • Self-Learning Knowledge Base: Adapts to project-specific command patterns and user corrections, continuously improving its accuracy and relevance over time.
  • Use Case: Before a major software release, use this Skill to automatically scan all your README.md and docs/ files. It will verify every npm, git, docker, or custom CLI command, flagging any that are broken or outdated, so you can fix them before they reach your users.

Quick Start

Verify all commands in the project's markdown documentation.

Frequently Asked Questions about command-verify

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

FAQPage Schema
How do I verify that commands in my markdown documentation are still accurate?

Command verification scans code blocks and inline commands across all markdown files in your repository to catch broken or outdated instructions before they reach users. This Skill automatically discovers commands, validates them, and flags those that need updating.

Can I automate checking documentation without manually testing every command?

Yes. This Skill automates the discovery and verification of documented commands in markdown files, categorizing them as safe, conditional, or dangerous to control execution risk while eliminating manual checking overhead.

How does this tool avoid rechecking commands that haven't changed?

Git-diff-based caching identifies only modified files and revalidates affected commands, eliminating redundant checks and achieving zero token cost after initial setup by skipping unchanged documentation.

What types of commands can this Skill find and verify in documentation?

This Skill discovers and validates npm, git, docker, and custom CLI commands embedded in code blocks and inline across markdown documentation, applying consistent verification logic across all command formats.

When should I run command verification before releasing software?

Run verification before major releases to scan README and docs files for broken or outdated commands, ensuring users receive accurate instructions and preventing support issues from documentation errors.

Does this approach work with git-based repositories?

Yes. This Skill requires git and uses git-diff-based caching to track changes, store validation metadata per commit, and revalidate only affected commands—essential for efficient, repeatable verification workflows.