Testing

This is the runtime counterpart to auditing. It spins up a dev marketplace, installs your bundle-plugin locally, runs your hooks to see if they actually fire, and checks whether components are discoverable across platforms. The cross-platform readiness phase is genuinely useful because it catches things like Claude Code's plugin caching breaking relative paths or Cursor losing bootstrap state after clear. Most developers skip the local install step and regret it later. Use this before any release, right after audit passes but before you bump the version. The test report goes into your audits folder and will block the release pipeline if it finds critical issues.

GitHub stars: 297
last updated: Apr 27, 2026

View on GitHub

Install

$ npx -y skills add odradekai/bundles-forge --skill testing --agent claude-code

Installs into .claude/skills of the current project.

Files

Testing Bundle-Plugins

Overview

Dynamic verification of a bundle-plugin project: install it locally, confirm components are discoverable, validate hooks fire correctly, and run cross-platform smoke tests. Complements bundles-forge:auditing (static analysis) with runtime validation.

Core principle: Audit tells you if the structure is correct; testing tells you if it actually works.

Skill type: Flexible — adapt the test scope based on target platforms and project maturity.

Announce at start: "I'm using the testing skill to verify this plugin works correctly."

Step 1: Resolve Input & Detect Scope

Input Normalization

The target must be a local bundle-plugin project (has package.json + skills/). Remote URLs and archives are not supported — testing requires a local working directory.

Scope Detection

Target	Mode
Project root with multiple platforms	Full testing — all 5 test phases
Project root with single platform	Platform testing — phases 1-4 for the target platform
Single skill directory	Skill-only testing — phase 3 (component discovery) only