unikit-verify

Verify plan-to-code alignment, compilation, tests, and anti-patterns in changed files.

16|1|Updated Apr 20, 2026

Search Tags:#documentation #verification #code-quality #ci-cd #tests #plan-drift #engine-rules

Ready to run

npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unikit-verify
Source: https://github.com/NintendaDev/unikit-ai/tree/main/skills/unikit-verify
Command: npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure that a feature or patch implemented in a project actually matches the approved plan, compiles, passes tests, and follows project conventions.

Core Features & Use Cases

Plan-to-Code Verification: checks alignment between planned tasks and actual code changes.
Quality Gate: runs compile and tests checks, and enforces engine-specific rules.
Review Readiness: generates a verification report outlining gaps, drift, and suggestions for follow-up.

Quick Start

Run /unikit-verify to generate a verification report for the currently checked-out feature or branch.

Frequently Asked Questions about unikit-verify

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

FAQPage Schema

How do I check for plan drift between my implementation and the approved design?▼

Plan drift detection compares actual code changes on a feature branch against the planned tasks, reporting gaps with file:line references and remediation guidance.

How do I verify code builds and check for anti-patterns before a review?▼

Code verification runs compilation and test checks on changed files determined from the base branch, flagging TODOs and anti-patterns to ensure review readiness.

What's the best way to ensure all planned tasks are completed in a feature patch?▼

Plan-to-code verification aligns implementation patches with planned tasks, identifying incomplete items and generating a verification report outlining gaps and suggestions.

Does the verification process enforce engine-specific rules for my project?▼

Engine-specific rules are enforced during the quality gate check, applying project conventions to changed files and reporting violations with file:line references.

Can I use this to verify only the changed files on a feature branch?▼

Verification scope targets changed files determined from the base branch, ensuring compile checks, tests, and anti-pattern scans focus solely on your implementation patch.

Why does my implementation fail the quality gate even when it compiles?▼

Quality gate failures occur when tests fail, engine-specific rules detect anti-patterns, or plan-to-code verification identifies drift between the plan and implementation.