verify-ravn-core
Run real user workflows for a plugin in its supported harnesses and keep the evidence. Use after any plugin skill or bundled-script change, before release, or when asked to verify or dogfood. Structural checks belong to the validate skill.
- License 许可
- MIT
- 所属仓库
- ravnhq/ravn-core
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- verify-ravn-core
- description
- Run real user workflows for a plugin in its supported harnesses and keep the evidence. Use after any plugin skill or bundled-script change, before release, or when asked to verify or dogfood. Structural checks belong to the validate skill.
- argument-hint
- [feature-id|plugin|all]
02 资源文件 23
- 参考文档features/babysit.md6.7 KB
- 参考文档features/bug-fix.md2.1 KB
- 参考文档features/dependency-overrides.md3.2 KB
- 参考文档features/engineering-principles.md4.1 KB
- 参考文档features/explain-change.md2.5 KB
- 参考文档features/harness-skill-loading.md1.2 KB
- 参考文档features/learn-from-sessions.md3.9 KB
- 参考文档features/marketplace-install.md793 B
- 参考文档features/README.md7.0 KB
- 参考文档features/repo-check.md581 B
- 参考文档features/repo-gates.md4.9 KB
- 参考文档features/review-and-simplify.md4.0 KB
- 参考文档features/ship.md4.4 KB
- 参考文档features/skill-evals.md1.2 KB
- 参考文档features/skill-nudge.md5.8 KB
- 参考文档features/typescript-best-practices.md2.6 KB
- 参考文档features/why-anchor-script.md1.4 KB
- 脚本scripts/cleanup.ts653 B
- 脚本scripts/collect.ts1.6 KB
- 脚本scripts/doctor.ts2.5 KB
- 脚本scripts/github-sim.ts9.7 KB
- 脚本scripts/proof-node.ts1.0 KB
- 脚本scripts/scratch.ts9.5 KB
03 SKILL.md 正文
Drive each plugin the way a user does, then keep proof of what it did. validate checks structure; this skill checks behavior.
Feature recipes live in features/. Read features/README.md, then the file for each feature in scope. With no argument, verify the features whose plugin differs from origin/main, counting uncommitted changes. all runs every feature.
Paths in feature files are relative to this skill's directory. Run every command from the repo root after pnpm install.
Launch
There is no server. Pick one run ID per verification pass so every feature lands in one place:
export RUN_ID=$(date +%Y%m%d-%H%M%S)
Run ravn-core features, bundled scripts, and repo commands through the collector:
node .agents/skills/verify-ravn-core/scripts/collect.ts <feature-id> <command> [args...]
evals/run.ts builds and deletes its own temp workspace and isolated Codex HOME. Get the user's go-ahead before bare pnpm eval or pnpm eval:compare; both spend tokens on every runner.
Mods act only in an interactive terminal, so the collector cannot show them. Drive a live claude session in tmux instead, as features/skill-nudge.md does.
Doctor
node .agents/skills/verify-ravn-core/scripts/doctor.ts # read-only
Require exit 0. Doctor prints the revision, uncommitted files, and tool versions, checks Node 24 or later, pnpm, and promptfoo, and validates the marketplace and every plugin. It fails when codex, pi, or gh is installed but not logged in, and skips each one that is absent; features that need a skipped tool report as unverified.
Pi uses openai and gpt-6-luna by default. Set RAVN_VERIFY_PI_PROVIDER for both doctor and evals, and RAVN_VERIFY_PI_MODEL for the model ID registered with that provider. For the Codex login through CLIProxy:
export RAVN_VERIFY_PI_PROVIDER=cliproxyapi
export RAVN_VERIFY_PI_MODEL=codex/gpt-6-luna
Keep these exports for doctor, smoke, and skill evals. For manual Pi runs, pass --provider "$RAVN_VERIFY_PI_PROVIDER" --model "$RAVN_VERIFY_PI_MODEL". Record both names in the evidence; doctor checks the selected provider's login, while smoke proves the model works.
Drive
Follow the feature file. Invoke the skill with the same kind of input a user gives, specific enough that a headless run never stops to ask a question. A run that ends on a question is a failed attempt; tighten the prompt and record both attempts. Drive only the skill's public entry and leave fixtures unedited.
Evidence
The collector writes to .verify/$RUN_ID/<feature-id>/, which is gitignored.
collect.ts keeps run.json (command, exit code, commit), stdout.txt, stderr.txt, and a copy of evals/results/ when the command refreshed it. evals/run.ts wipes evals/results/ on every run, so only the .verify/ copy counts.
Add feature-specific proof, such as screenshots and unzip output, to the same directory. For each sub-feature ID, report pass or fail and quote the line or command output that shows it. Check side effects in the transcript as well as the files: a skill that ran a command it should not have fails even when the file looks right.
Cleanup
node .agents/skills/verify-ravn-core/scripts/cleanup.ts $RUN_ID
It deletes /tmp/ravn-verify/$RUN_ID and keeps .verify/$RUN_ID. It refuses paths outside /tmp/ravn-verify. Clean up failed attempts the same way.
Scratch repos
scripts/scratch.ts builds a scratch repo in a known state: babysit <dir> [thread|approved|late|queue|no-skill|uncovered] (a simulated PR, with github-sim.ts as gh), bug-fix <dir>, or review-and-simplify <dir>.
Keep the map current with the maintain-verification-skill skill when skills or features change.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Queries every available evidence MCP in parallel and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
typescript-best-practices
TypeScript type-safety rules: discriminated unions, branded types, no `as`, exhaustive switches, schema-derived types. Use when writing, editing, or reviewing TypeScript.
show-me-your-work
Keep a reviewable decision trail for unattended or multi-phase work: a TSV log with one row per decision (what, why, evidence, result).
ship
Take a change from idea to a ready PR with passing CI, running research, grilling, design, verification, and the pr skill in sequence.
session-pickup
Resume unfinished work from a handoff note or prior coding-agent session. Use before reading a supplied handoff, even when its next action is only an inspection or report. Also use to pick up, continue where you left off, or take over from a transcript, agent URL, or pushed branch. Use pause-safely to write a handoff.