team-shinchan:verify-implementation

Discover and run all verify-* skills to generate a unified validation report.

8|2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-verify-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-shinchan:verify-implementation
Source: https://github.com/seokan-jeong/team-shinchan/tree/main/skills/verify-implementation
Command: npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-verify-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated end-to-end verification by executing all verify-* validators to produce a unified report.

Core Features & Use Cases

  • Orchestrates discovery of all verify-* skills
  • Executes validators sequentially with status aggregation
  • Generates consolidated PASS/FAIL report and per-skill visibility

Quick Start

Invoke the verify-implementation skill to run all validators and generate the integrated report immediately.

Frequently Asked Questions about team-shinchan:verify-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate running multiple validation plugins in CI and generate a single report?

You can orchestrate automated verification by discovering and sequentially running all verify-* skills to produce a unified PASS/FAIL report with per-skill visibility, ensuring traceable end-to-end results in CI-like environments.

What is the best way to execute all verify-* validators sequentially for plugin-driven QA?

You execute verify-* validators sequentially by reading each skill's SKILL.md for commands at the plugin root, aggregating statuses, and generating a consolidated validation report to ensure complete plugin-driven QA coverage.

How does verification orchestration handle missing SKILL.md entries during validation?

The verification orchestration handles missing SKILL.md entries with graceful warnings, allowing the automated validation process to continue running other discovered verify-* skills without failing the entire execution context.

Do I need an execution context at the plugin root to run automated verification?

Yes, an execution context at the plugin root is required to run automated verification, as the orchestration needs to locate the directory to discover all available verify-* skills and read their SKILL.md commands.

Can I get per-skill visibility when running end-to-end validation across multiple validators?

You get per-skill visibility in the consolidated validation report, which aggregates individual PASS/FAIL statuses from each verify-* skill executed during the end-to-end validation orchestration.