core/verifier

Reviews Redux and documentation diffs against compliance, reuse, and state-integrity gates.

6|6|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/intent-hq/cloudlands-fe --skill core-verifier-intent-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: core/verifier
Source: https://github.com/intent-hq/cloudlands-fe/tree/main/.agents/skills/themis/core/verifier
Command: npx skills add https://github.com/intent-hq/cloudlands-fe --skill core-verifier-intent-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews of Redux state changes, refactors, and skill documentation often rely on subjective judgment, letting derived state, duplicate utilities, and pass-through wrappers slip through without verifiable evidence. ## Core Features & Use Cases - Seven-Gate Review Sequence: Enforces instruction compliance, refactor cleanup, utility reuse, state integrity, canonical ownership, automated validation, and semantic checks on every diff. - Evidence-Based Acceptance: Requires commands, exit codes, and search results in every verification report instead of shallow approvals. - Automated Gate Selection: Maps diff scope to required checks such as git diff --check, npm run validate:architecture, npm test, npm run build, and npm run validate:release. - Use Case: When a teammate moves a Redux slice and adds a new selector, run this gate sequence to confirm no pass-through wrapper remains, the selector derives values from canonical state, and architecture validation passed. ## Quick Start Review the current git diff against the verifier quality gates and produce a report citing the instructions checked, gate commands run, and any blockers.

Frequently Asked Questions about core/verifier

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

FAQPage Schema
How do I verify a Redux state change before accepting a diff?▼

Run the seven-gate sequence: instruction compliance, refactor cleanup, utility reuse, state integrity, canonical owners, automated validation, and semantic checks. Each gate requires concrete evidence such as search results, command exit codes, or diff checks before approval.

What checks catch derived or duplicated Redux state in code review?▼

The state integrity gate hard-fails state containing filtered lists, counts, has* booleans, or duplicated entity records alongside a Collection. Derived values must be implemented as selectors, and npm run validate:architecture provides automated enforcement.

When is npm run validate:architecture required during review?▼

It is required for diffs touching Redux state, actions, selectors, sagas, reducer or slice behavior, component/store import boundaries, localStorage access, collection state, pass-through wrappers, or the skills and docs governing those areas.

Why does a refactor review fail on pass-through wrappers?▼

The refactor cleanup gate hard-fails old modules that only re-export symbols from a new path or delegate to the new implementation. A remaining shim is accepted only with an adjacent comment naming the compatibility reason and removal condition.

Can a verifier approve a diff based only on passing tests?▼

No. Tests alone cannot prove state ownership or instruction compliance. Approval requires evidence for every applicable gate, including searches for duplicate owners, reuse discovery for new helpers, and automated gate results with exit codes.