Skill

verify

Runs plugin integrity checks: automated test suite (bats-core), ShellCheck linting, JSON validation, cross-references, and MCP tools. Use after changes, before PRs, or when broken.

Bash

Markdown

testing

code-quality

npx claudepluginhub archcore-ai/plugin --plugin archcore

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Comprehensive plugin integrity verification. Run after structural changes to the plugin.

SKILL.md

Similar Skills

claude-plugin-audit

Audits Claude Code plugins for structure, quality, and best practices in plugin.json, commands, agents, skills, and hooks. Outputs severity-ranked issues with remediation steps.

1 tool

outfitter

plugin-validator

1.9k

Validates Claude Code plugin structure, JSON schemas, frontmatter, security compliance, script permissions, and marketplace consistency using CI-like checks.

10 files3 tools

jeremy-plugin-tool

plugin-validator

Validates Claude Code plugin structure including plugin.json syntax and required fields. Audits hooks for silent failures in bash and Python scripts before release.

3 files5 tools

plugin-dev

Stats

Stars11

Forks2

Last CommitApr 13, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

/archcore:verify

Comprehensive plugin integrity verification. Run after structural changes to the plugin.

When to use

After modifying bin/ scripts, hooks, skills, agents, rules, or JSON configs
Before creating a pull request
After merging upstream changes
When something seems broken

Execution

Step 1: Run automated test suite

Run the test suite using Bash:

make test

If bats-core is not installed, install it first: brew install bats-core (macOS) or apt install bats (Linux).

Report: total tests, passed, failed. If any fail, list the failed test names and investigate.

Step 2: Run ShellCheck (if available)

make lint

If shellcheck is not installed, skip this step and note it.

Step 3: JSON config quick-check

make check-json

Step 4: Manual cross-reference verification

Only if tests pass. Check these items that automated tests may not fully cover:

README accuracy: Verify the skill count, agent count, and hook count in README.md match reality:
- Count skills: ls -d skills/*/SKILL.md | wc -l
- Count agents: ls agents/*.md | wc -l
- Compare with numbers stated in README.md
Archcore docs consistency: If .archcore/ documents describe plugin components (component-registry.doc.md, plugin-architecture.spec.md), spot-check that they reflect current state.
MCP server availability: Run mcp__archcore__list_documents() to verify MCP tools are functional. If it errors, report the error.

Step 5: Live hook smoke test (optional)

If the user wants a deeper check:

Try writing to a .archcore/*.md file using the Write tool — it should be blocked by the PreToolUse hook.
Create a test document using mcp__archcore__create_document — the PostToolUse hook should validate afterward.

Output Format

Present results as:

## Plugin Verification Report

| Phase | Status | Details |
|-------|--------|---------|
| Test suite (N tests) | PASS/FAIL | X passed, Y failed |
| ShellCheck | PASS/SKIP | clean or N warnings |
| JSON configs | PASS/FAIL | all valid or which failed |
| Cross-references | PASS/WARN | any mismatches found |
| MCP tools | PASS/FAIL | functional or error |

**Result: X/Y phases passed.**

If any phase fails, list specific issues as action items.