devkit-test
Auto-fix discoverable issues
What this skill does
# 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 in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.