Skip to content

SKILL.md

Latest commit

 

History

History
44 lines (34 loc) · 1.88 KB

SKILL.md

File metadata and controls

44 lines (34 loc) · 1.88 KB
name verify-this
description 验证一个具体声明是否成立。用户说“verify this / 证明它好了 / 看看是否修复 / 给证据 / 是否真的变快”等需要 before/after、本地测试、日志、截图或构建产物证据时使用。

Verify This

Use this skill to prove or disprove a falsifiable claim with local evidence. Do not turn it into a recap.

Workflow

  1. Restate the claim in measurable form: condition, expected behavior, and pass/fail threshold.
  2. Pick the smallest local surface that can disprove it:
    • TypeScript behavior: focused unit test, npm run test:unit, or a small repro.
    • Workspace packages: npm run test --workspaces --if-present.
    • Compile safety: npm run type-check.
    • Lint safety: npm run lint.
    • Android/native behavior: cd android && ./gradlew assembleDebug --no-daemon.
    • UI behavior: local screenshot or browser/app interaction evidence when applicable.
  3. Capture baseline and treatment with the same command, input, environment, and threshold.
  4. If a real baseline is unavailable without reverting user changes, say so and use INCONCLUSIVE; do not reset or overwrite user work.
  5. Compare raw artifacts, not impressions.
  6. Return exactly one verdict: VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

Guardrails

  • Never modify .env files.
  • Never run destructive git commands to create a baseline.
  • Keep artifacts minimal; prefer terminal output snippets unless screenshots/logs are necessary.
  • If writing artifacts, use /tmp/verify-this/<claim-slug>/, not the repo, unless the user asks.
  • Do not soften a negative result. A clear NOT VERIFIED is useful.

Output

VERIFIED | NOT VERIFIED | INCONCLUSIVE
Claim: <falsifiable claim>

Evidence:
- <command/artifact>: baseline=<...>, treatment=<...>, delta=<...>, threshold=<...>

Reasoning:
<one concise paragraph naming evidence and confounds>