verify

Solid

Drive/evidence recipe for verifying wenlan changes at their real surfaces (daemon HTTP, CLI, MCP stdio). The handle file the built-in verify protocol expects; launch primitives live in the run-wenlan skill, deeper machinery (mutation audit, behavior trace, weekly sweep) in the prove skill.

AI & Automation 47 stars 5 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 78/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Verifying wenlan — drive the real surfaces Launch: use the `run-wenlan` skill — build, isolated boot on :17878, stop, and the daemon lifecycle checklist all live there. Never verify against the shared prod daemon on :7878. Drive by surface — these scripts ARE the drive recipes (read them for the flow, run them for a full round-trip): - Daemon HTTP: curl the changed route on the isolated port; recipe in `.claude/skills/prove/references/daemon.md`. - CLI: `bash scripts/smoke-cli.sh` (capture → memories → search, black-box). - MCP: `bash scripts/smoke-mcp.sh` (stdio JSON-RPC initialize → capture → recall). Gotchas (drive-time): - Ingest is async (batcher + embedding): poll search up to ~60s before calling a miss a failure. - Record evidence: prefix any check with `~/.claude/bin/attest.sh`. Deeper verification — mutation audit (`suite`), behavior trace (`behaviors`), weekly verify-the-verifier (`sweep`): invoke the `prove` skill.

Details

Author: 7xuanlu
Repository: 7xuanlu/wenlan
Created: 3 months ago
Last Updated: today
Language: Rust
License: Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

prove

Per-surface verification loops for wenlan — daemon, cli, mcp, plugin, suite strength (mutation), behavior trace, weekly sweep. Routes to scripts; every check records evidence via attest. Deeper than the built-in verify skill — use prove for mutation audits, behavior tracing, and the weekly sweep; built-in /verify handles generic runtime observation.

47 Updated today

7xuanlu

Testing & QA Listed

verify

Verify an engine change end-to-end by rendering the bundled fixture (examples/local-demo) and inspecting the output MP4 and intermediates. Use when the user says "verify", "run the smoke test", "e2e this change", "does the fixture still render", or before committing a nontrivial engine change. Knows the gotchas: OPENAI_API_KEY (or a local OPENAI_BASE_URL server) is needed for voice/captions but not probe/record/compose, stage-by-stage re-runs beat full re-renders, AIDEMO_KEEP_TMP=1 keeps .compose-tmp for compose debugging, logs/fail-*.png from failed takes. Do NOT use for: recording real product demos (use record-demo) or doc-only changes with no runtime surface.

1 Updated today

tandryukha

Code & Development Solid

verifier-setup

Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-local` skill + script, and the installed driver skill. Use when someone says "set up verification", "make this repo verifiable", "scaffold a verify skill", "set up the verifier".

1,102 Updated yesterday

AI-Builder-Club