Best use case
devkit-test is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
Auto-fix discoverable issues
Teams using devkit-test should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/devkit-test/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How devkit-test Compares
| Feature / Agent | devkit-test | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Auto-fix discoverable issues
Which AI agents support this skill?
This skill is designed for Codex.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# 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 **Framework Tests**: - [ ] Phases defined in manifest - [ ] Flow documents exist for each phase - [ ] actors-and-templates.md exists - [ ] config/models.json exists - [ ] metrics/tracking-catalog.md exists ### 5. Run Deployment Test Simulate deployment to temporary directory: ```bash # Create temp test directory mkdir -p /tmp/aiwg-test-$$ # Attempt deployment aiwg -deploy-agents --source <package-path> --target /tmp/aiwg-test-$$ --dry-run # Check expected output structure ``` ### 6. Auto-Fix (if --fix) When `--fix` is specified, attempt to repair: **Fixable Issues**: - Missing directories → Create them - Manifest component arrays out of sync → Update from files - Missing README.md → Generate from manifest - Invalid JSON formatting → Reformat **Non-Fixable Issues** (report only): - Missing required fields in manifest - Invalid agent/command content - Missing parent framework (extensions) ### 7. Generate Report **Summary Format**: ``` Package Test: <package-id> Type: <addon|extension|framework> ───────────────────────────────── Structure Tests: <pass/fail count> Content Tests: <pass/fail count> Type Tests: <pass/fail count> Deployment Test: <pass/fail> Overall: <PASS|FAIL> ``` **Detailed Format (--verbose)**: ``` Package Test: <package-id> ───────────────────────────────── [Structure Tests] ✓ manifest.json exists ✓ manifest.json is valid JSON ✓ Required fields present ✓ agents/ directory exists ✗ commands/ directory missing ... [Content Tests] ✓ agent-one.md: valid frontmatter ✓ agent-one.md: valid model (sonnet) ✗ agent-two.md: missing tools field ... [Type Tests] ✓ No requires field (addon) ... [Deployment Test] ✓ Dry-run deployment successful [Issues Found] ERROR: commands/ directory missing WARNING: agent-two.md missing tools field [Auto-Fixed] (if --fix) ✓ Created commands/ directory ``` ## Exit Codes - 0: All tests passed - 1: Tests failed (fixable issues remain) - 2: Tests failed (non-fixable issues) ## Examples ```bash # Test addon /devkit-test aiwg-utils # Test with verbose output /devkit-test sdlc-complete --verbose # Test and auto-fix /devkit-test my-addon --fix --verbose # Test extension /devkit-test sdlc-complete/extensions/hipaa ``` ## References - @$AIWG_ROOT/agentic/code/addons/aiwg-dev/README.md — aiwg-dev addon overview - @$AIWG_ROOT/docs/extensions/overview.md — Extension system architecture and package types - @$AIWG_ROOT/docs/cli-reference.md — CLI reference including validate-metadata command - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Verification-before-action pattern - @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/README.md — SDLC framework as example test target
Related Skills
pytest-runner
Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.
vitest-runner
Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.
test-sync
Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation.
test-coverage
Analyze test coverage reports, identify gaps by priority, and recommend test improvements with trend tracking
mutation-test
Run mutation testing to validate test quality beyond code coverage. Use when assessing test effectiveness, finding weak tests, or validating test suite quality.
generate-tests
Generate comprehensive test suite for $ARGUMENTS following project testing conventions and best practices.
flow-test-strategy-execution
Orchestrate comprehensive test strategy with test suite execution, coverage validation, defect triage, and regression analysis
devkit-validate
Validate addon, framework, or extension structure and manifest
devkit-create-skill
Enable interactive design mode
devkit-create-framework
Comma-separated phase names
devkit-create-extension
Create a new AIWG extension (framework expansion pack) with AI-guided setup
devkit-create-command
Create a new slash command with AI-guided behavior definition