Skill

verification

Activates after code changes to suggest or run verification steps. Provides test-after-action patterns for different file types and frameworks.

Install

npx claudepluginhub theglitchking/aeon-flux --plugin aeon-flux

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Code has been modified. Verify the changes work.

SKILL.md

Similar Skills

github-deep-research

2 files

Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.

bytedance-deer-flow-1

63.9k

surprise-me

Dynamically discovers and combines enabled skills into cohesive, unexpected delightful experiences like interactive HTML or themed artifacts. Activates on 'surprise me', inspiration, or boredom cues.

bytedance-deer-flow-1

63.9k

image-generation

2 files

Generates images from structured JSON prompts via Python script execution. Supports reference images and aspect ratios for characters, scenes, products, visuals.

bytedance-deer-flow-1

63.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitJan 14, 2026

Actions

View Source View Plugin View on GitHub View README

Verification Mode

Code has been modified. Verify the changes work.

Verification by File Type

JavaScript/TypeScript

# Type check
npx tsc --noEmit

# Run tests
npm test

# Lint
npm run lint

# Quick syntax check
node --check file.js

Python

# Syntax check
python -m py_compile file.py

# Type check
mypy file.py

# Run tests
pytest

# Lint
ruff check file.py

Go

# Build check
go build ./...

# Run tests
go test ./...

# Vet
go vet ./...

Rust

# Check without building
cargo check

# Run tests
cargo test

# Clippy
cargo clippy

Shell Scripts

# Syntax check
bash -n script.sh

# ShellCheck
shellcheck script.sh

Docker

# Validate Dockerfile
docker build --check .

# Or dry run
docker build -t test .

Verification Strategy

After Single File Edit

Run file-specific syntax check
Run related unit tests
If both pass, continue

After Multi-File Changes

Run full type check / build
Run affected test suites
If CI exists, trust CI for full verification

After Config Changes

Validate config syntax (JSON, YAML, etc.)
Test with dry-run if available
Check dependent services start

Quick Verification Commands

# JSON syntax
jq . file.json > /dev/null

# YAML syntax
python -c "import yaml; yaml.safe_load(open('file.yaml'))"

# Package.json
npm ls 2>&1 | head -5

# Git status (verify staged correctly)
git diff --cached --stat

When to Skip Verification

Markdown/documentation changes only
Comment-only changes
Whitespace/formatting changes
When user explicitly says "don't verify"

Verification Output

Keep verification output minimal:

✓ Type check passed
✓ 12 tests passed

Or on failure:

✗ Type check failed: src/index.ts:45 - Type error
[Fix immediately without explanation]