verify

Verify artifacts against Pack standards and session context with PASS/FAIL/CONDITIONAL verdicts.

44|125|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/TserenTserenov/FMT-exocortex-template --skill verify-tserentserenov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/TserenTserenov/FMT-exocortex-template/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/TserenTserenov/FMT-exocortex-template --skill verify-tserentserenov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that an artifact matches the Pack-defined standard and session context, preventing regressions, scope creep, and undocumented deviations during development and acceptance.

Core Features & Use Cases

  • Context-isolated verification: Launches a sub-agent with context isolation to evaluate results rather than process, protecting reviewer objectivity.
  • Multi-modal checks: Supports code reviews, ArchGate assessments, Pack capture validation, work-product acceptance, chain-of-verification across downstream consumers, and adversarial pre-mortem checks.
  • Structured verdicts: Produces PASS / FAIL / CONDITIONAL verdicts with a severity-tagged discrepancy table and concise remediation recommendations for maintainers and reviewers.
  • Use Case: Use when a pull request touches multiple components to ensure outputs, contracts, and Pack principles remain consistent and to identify unreviewed downstream consumers.

Quick Start

Use the verify skill to check a changed file against Pack standards by saying: verify code src/main.py

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify code changes against Pack standards before a release?

Verifying code changes against Pack standards requires evaluating git diffs and work-product context against Pack manifests and principles, producing PASS, FAIL, or CONDITIONAL verdicts with remediation recommendations.

What is chain-of-verification analysis for code review?

Chain-of-verification analysis for code review is an adversarial scope check evaluating unreviewed downstream consumers, ensuring outputs, contracts, and Pack principles remain consistent across multiple components touched in a pull request.

How do I perform an isolated architectural review of a git diff?

Performing an isolated architectural review involves spawning a context-isolated sub-agent with a predefined checklist to evaluate the git diff objectively, protecting reviewer objectivity by assessing results rather than process.

Does Pack capture validation work with work-product acceptance checks?

Pack capture validation works with work-product acceptance checks by applying multi-modal checks to session context, generating severity-tagged discrepancy tables and concise remediation recommendations for maintainers and reviewers.

Can I use adversarial pre-mortem checks to prevent scope creep in pull requests?

Adversarial pre-mortem checks can prevent scope creep in pull requests by validating artifacts against Pack-defined standards and session context, identifying undocumented deviations and downstream consumer impacts before release validation.