hotline-tdd SKILL.md skillA
hotline-tdd from sc-10749/hotline is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sc-10749/hotline/hotline-tdd@git:20261026.24dfdd6Pins git:20261026.24dfdd6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sc-10749/hotline
- Path
skills/hotline-tdd/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261026.24dfdd6, committed Oct 26, 2026
- Size
- 9,018 bytes
- Repository stars
- 210
- License
- none declared
Use when implementing or fixing behavior in Hotline and you need to clarify acceptance criteria, choose the repository's real checks, or retry only the affected scope.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Hotline TDD ## 目的 本 Skill 将 Hotline 的需求澄清、规格确认、TDD、最小范围重试和交付评审串成一个可验证流程。它补充 Superpowers 的 `test-driven-development`,不替代仓库根目录 `AGENTS.md` 中的规则。 **核心原则:** 每个新行为先用测试表达,再观察测试按预期失败;用最小实现让它通过,最后运行本仓库适用的交付检查。 ## 适用范围 - 新功能、行为变更和 Bug 修复。 - 因测试失败而需要局部修复或重试的任务。 - 跨前后端或多阶段工作,需要把需求映射到测试和评审结果的任务。 纯文档修改按 `AGENTS.md` 核对路径、命令、端口、模块名称和验证命令;不要为纯文档内容伪造代码测试。 ## 流程 ### 1. 澄清需求 先阅读根目录 `AGENTS.md` 及相关子目录规则,再查看目标代码、现有测试和 Git 工作区状态。常规需求澄清和测试不得依赖读取 `.env`、真实数据库或凭据;只有任务明确要求诊断本地配置或数据时,才做最小只读检查,并确保真实值不出现在输出中。 把用户请求整理为可观察的验收条件,说明: - 哪些输入会触发行为,以及预期输出或状态。 - 哪些现有行为必须保留。 - 哪些内容不在本次范围。 - 哪些失败可以局部重试,哪些变化会影响其他任务。 如果答案会改变外部接口、持久化格式、权限、安全行为或交付范围,先向用户确认。小而明确的改动可直接陈述假设并继续。不要在每个 RED/GREEN 循环都请求批准。 ### 2. 确认规格和计划 为每项验收条件列出至少一个能验证它的行为测试,并标出实现文件与依赖关系。多步骤或跨模块任务使用 `brainstorming` 和 `writing-plans` 的流程;先让用户确认规格和计划,再实现。 一个测试应说明它捕捉哪种错误。优先检查真实行为,避免只断言源码文本、私有实现或 mock 调用次数。对本来就满足的行为,不要制造一个假的 RED。 ### 3. 记录基线并保护现有改动 开始编辑前查看 `git status --short`,区分本任务新改动与用户已有改动。只编辑本任务需要修改的部分,不覆盖、删除或重置用户已有改动。 先运行与目标相关、已有的测试,记录其结果。区分这次引入的失败与基线已有失败。不要为了清理基线失败而扩大本次改动范围。 如果用户已有实现代码在测试之前存在: - 保留该代码,先为目标行为补上测试。 - 若测试暴露缺陷,再由测试驱动最小修复。 - 若测试立即通过,说明行为已经存在;不要删除用户代码或改写测试来制造失败。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_sbs7huw7dxzi7sca/33a79c5b3296803460f3407e5c41a7fadb284faba33c88d0cab93ec41b1b8a54.json
Then /plugin install hotline-tdd@markdownregistry-sbs7huw7dxzi7sca in Claude Code. It installs git:20261026.24dfdd6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add sc-10749/hotline/hotline-tdd@sha256:33a79c5b32968034The line at the top of this page pins the label git:20261026.24dfdd6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_sbs7huw7dxzi7sca)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in sc-10749/hotline/hotline-tdd since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of hotline-tdd from somewhere else? Ask it: where did my hotline-tdd come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 26, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/hotline-tdd/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9018 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sc-10749/hotline · 210 stars · license none declared · pushed 2026-11-15 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_sbs7huw7dxzi7sca GET https://markdownregistry.com/api/v1/resolve?ref=sc-10749/hotline/hotline-tdd GET https://markdownregistry.com/api/v1/blob/33a79c5b3296803460f3407e5c41a7fadb284faba33c88d0cab93ec41b1b8a54
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.