N98\Magento\Command\MagentoConnect\ValidateExtensionCommand::configure PHP Method

    protected function configure()
    {
        $this->setName('extension:validate')->addArgument('package', InputArgument::OPTIONAL, 'Package_Module to check')->addOption('skip-file', null, InputOption::VALUE_NONE, 'If set, command will skip reporting the existence of package files')->addOption('skip-hash', null, InputOption::VALUE_NONE, 'If set, command will skip validating the package file hashes')->addOption('full-report', null, InputOption::VALUE_NONE, 'If set, command will report on ALL package files')->addOption('include-default', null, InputOption::VALUE_NONE, 'Include default packages that ship with Magento Connect')->setDescription('Reads Magento Connect Config, and checks that installed package files are really there');
        $help = <<<HELP
Reads Magento Connect config, and checks that installed
package files are really there.

Magento Connect is Magento's built in package manager.  It's
notorious for failing to completly install extension files
if file permissions are setup incorrectly, while telling a
Connect user that everything is OK.

This command scans a the list of packages installed via
Magento Connect, and uses the package manifest to check

1. If the file actually exists

2. If the file hash matches the hash from the manifest

A missing file indicates a package wasn't installed
correctly.  A non-matching hash *might* mean the file's been
changed by another process, or *might* mean the file is from
a previous package version, or *might* mean the extension
packager failed to generate the hash correctly.

This is the madness of using software that lies.

HELP;
        $this->setHelp($help);
    }