Skip to main content

prove

Show a failing check, then a passing one, on real behavior.

来源信息

仓库
Belweave/hstack
最近来源活动
2026年10月28日 12:24
检测到的 SKILL.md 语言
英语
星标
1
Forks
0

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
prove
description
Show a failing check, then a passing one, on real behavior.
version
0.2.1
author
Preetham Kyanam
license
MIT
platforms
["linux","macos","windows"]
metadata
{"hermes":{"tags":["testing","verification"],"related_skills":["test-driven-development","dogfood","ship"]}}
# Prove ## When to Use The change is supposed to be done, or the user asked for a report of what to run. Load this after `shape`, or after bundled `systematic-debugging`. ## What to do Done means a check you ran. Show it failing for the right reason, then passing. Name the surface you exercised: the CLI, the API, the job, the webhook, or the page. A unit test that never calls that surface is not this check. Run the check with `terminal`. Report-only mode lists the check, the command, and the expected failure. Do not edit product code in that mode. A performance claim names the limiter, how many times you repeated it, and the error. Otherwise it is not a result. An unvetted number is not a result. Do not restate bundled skills. Load them with `skill_view`: - A bug with a cheap unit test: `test-driven-development`. - Browser exploration of a page: `dogfood`. Use `browser_exec` only as that skill directs. When the passing check is real, stop. Opening a pull request is `ship`, and only when the user asks.
在 GitHub 查看