Devkit Test logo

Devkit Test

Community
jmagly
devkit-test

Auto-fix discoverable issues

Overview

Publisherjmagly
Repositoryaiwg
Skill namedevkit-test
Stars
225
Forks
34
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by jmagly on GitHub. Read the source before you install it.

Installation

Install the Devkit Test AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/jmagly/aiwg/tree/main/agentic/code/addons/aiwg-dev/skills/devkit-test
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jmagly/aiwg.git /tmp/aiwg
mkdir -p .claude/skills
cp -r /tmp/aiwg/agentic/code/addons/aiwg-dev/skills/devkit-test .claude/skills/devkit-test
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Devkit Test in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Devkit Test on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Devkit Test is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Frequently asked questions

What does the Devkit Test AI skill do?

Auto-fix discoverable issues

Why use Devkit Test on TypingMind?

Because you install it once and use it with any model. Devkit Test is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Devkit Test in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jmagly/aiwg/tree/main/agentic/code/addons/aiwg-dev/skills/devkit-test. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Devkit Test?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Devkit Test?

As many as you like. As long as a model supports skills, you can use Devkit Test with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Devkit Test AI skill free?

Yes. It is published on GitHub by jmagly under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇