Results for “realphonevalidation”

Verify that a change really works before you claim completion

Claude Code 会话的全面验证系统。

Schema validation for notes. Checks against domain-specific templates. Validates required fields, enum values, description quality, and link health. Non-blocking — warns but doesn't prevent capture. Triggers on "/validate", "/validate [note]", "check schema", "validate note", "validate all".

Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.

Runs a comprehensive mobile QA audit covering permissions, deep links, push notifications, offline mode, background/foreground transitions, memory leaks, network conditions, accessibility, and platform edge cases for Flutter, React Native, and native iOS/Android apps.

Verify TPM measured boot integrity and remote attestation using tpm2-tools, including PCR reading, event log replay, quote generation and verification, and golden baseline comparison.

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Live-device iOS QA for SwiftUI apps. (gstack)

阶段① 需求确认。以提问方式逐步确认需求，产出 design.md 第一章。

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

MiniCPM-V: A GPT-4V Level MLLM on Your Phone

Verifica que una implementación cumpla los specs del ciclo SDD ejecutando tests reales, revisando cobertura y emitiendo un veredicto de aprobación o rechazo.

Validate user claims against codebase and git history, trace to root cause, and propose a fix

Validate and confirm exploitability of vulnerabilities using the Metasploit Framework for risk-based prioritization and patch verification.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Detect abuse of legitimate Windows binaries (LOLBins) like certutil, regsvr32, mshta, and rundll32 using process telemetry, Sigma rules, and parent-child process analysis.

A validation *boundary* is any point where data crosses from a system you do not

Provides grep-based patterns to verify that code artifacts are real implementations rather than stubs or placeholders, covering React components, API routes, database schemas, and hooks.

Python data validation using type hints and runtime type checking with Pydantic v2's Rust-powered core for high-performance validation in FastAPI, Django, and configuration management.

Prevents AI agents from calling methods, imports, or variables that do not provably exist in the user's installed version, reducing hallucinated code.

Systematically explore a web application to find bugs and UX issues, producing a structured report with screenshots, repro videos, and detailed steps for each finding.

Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.

Prove a feature works by delegating verification to an independent sub-agent that drives the real app, then open a pull request with the proof.

Prove code works by running it, not just checking it exists. Verification through execution rather than inspection. Use after writing or modifying code to ensure it actually functions correctly.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Humanization Quality Verifier - Ensures transformation integrity and quality Validates that humanization preserves meaning, citations, and academic standards Use when: after G6 transformation, before final export, for quality assurance Triggers: verify humanization, check transformation, validate changes

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

Verify code changes work by running them. Proves through execution, not just inspection.