devkit-test

Test AIWG Package

Run comprehensive tests on an AIWG package to verify structure, functionality, and deployment readiness.

Process

1. Locate and Identify Package

Resolve the package path from $ARGUMENTS:

• If relative path, resolve from current directory
• If package name, look in addons/ and frameworks/

Identify package type from manifest.json:

• "type": "addon" → Addon tests
• "type": "framework" → Framework tests
• "type": "extension" → Extension tests

2. Run Structure Tests

Manifest Validation:

• manifest.json exists and is valid JSON
• Required fields present: id, type, name, version, description
• Entry paths exist and match actual directories
• Component arrays match actual files

Directory Structure:

• Expected directories exist (agents/, commands/, etc.)
• No orphaned files outside expected structure
• README.md exists and is non-empty

Component Files:

• All agents listed in manifest exist as .md files
• All commands listed in manifest exist as .md files
• All skills listed in manifest have SKILL.md
• All templates listed in manifest exist

3. Run Content Tests

Agent Validation: For each agent file:

• Valid YAML frontmatter with name, description, model, tools
• Model is valid (sonnet, opus, haiku)
• Tools list contains valid tool names
• Content sections present (Domain Expertise, Responsibilities, etc.)

Command Validation: For each command file:

• Valid YAML frontmatter with name, description
• Args defined with name and description
• Process section present
• No broken internal references

Skill Validation: For each skill:

• SKILL.md has valid frontmatter
• Trigger phrases defined
• Execution process documented
• References directory exists (if referenced)

4. Run Type-Specific Tests

Addon Tests:

• No requires field (addons are standalone)
• Can be deployed independently

Extension Tests:

• requires field present and valid
• Parent framework exists
• Located in correct extensions/ subdirectory