test-scenarios SKILL.md skillA

test-scenarios from jimyag/dotfiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add jimyag/dotfiles/test-scenarios@git:20261015.f79eac0

Pins git:20261015.f79eac0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
jimyag/dotfiles
Path
skills/test-scenarios/SKILL.md
Versions recorded
6
Latest version
git:20261015.f79eac0, committed Oct 15, 2026
First version recorded
Sep 18, 2026
Size
12,090 bytes
Repository stars
11
License
MIT

Use this skill when the user asks for a test plan, acceptance criteria, E2E checklist, or auditable scenario contract for a non-trivial change; do not use it for simple single-point edits or as a replacement for implementing tests.

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

# 测试场景契约

## 目标

在代码实现前把“什么行为必须成立”写成可追踪的场景清单,供实现、测试、评审和人工验收共同使用。场景契约描述验收边界,不是把所有测试代码提前写完。

## 何时使用

- 新功能或修复会改变用户、API、配置、数据、任务状态或外部服务行为。
- 变更跨越多个模块,存在边界、兼容性、权限、恢复或失败路径。
- 用户要求测试计划、验收标准、E2E 清单,或需要把验证结果整理成可审计文档。

## 何时不要使用

- 纯拼写、格式、注释或机械重命名。
- 需求和验证方式已经明确,且改动是局部、可逆的单点修改。
- 只需要执行已有测试,不需要新增行为边界。

## 输入与边界

先读取适用的项目指令、现有测试和相邻实现。明确目标、运行环境、外部依赖、成功标准和会改变验收判断的约束;事实可以从代码、文档或工具确认时,不要把它们变成用户问题。

如果目标仍有会实质改变结果的歧义,先转交 `brainstorming` 收敛目标,不要在场景表里猜测产品行为。不要因为缺少场景契约就擅自扩大实现范围。

## 最小流程

1. 写下本次变更的目标、关键约束和验收入口。
2. 读取现有测试,标记哪些行为已有覆盖,避免把历史测试重新当成新证据。
3. 按需要枚举:主流程、边界输入、错误处理、兼容性、权限/安全、并发/恢复和人工运行面。只保留会改变实现或验收判断的场景。
4. 为每个场景分配稳定 ID、类型、优先级和状态。
5. 将场景写入默认路径 `docs/dev/<run-slug>/test-scenarios.md`;如果已有 ADR,优先放在 ADR 旁边,使用同一个 slug。
6. 实现和验证过程中更新 `covered` 或 `skipped`,并在 `Evidence` 中记录测试路径、命令、日志、资源状态或跳过原因。
7. 如果包含 `e2e` 或 `manual` 场景,补一份短验收指南:准备条件、用户动作、可观察结果、场景 ID 映射,以及哪些结论仍只能由自动化验证证明。

如果用户只要求列出场景而没有授权写文件,直接在回复中输出契约,不创建持久文件。

## 场景契约格式

```markdown
# <任务名> 测试场景

## 范围

- 目标:...
- 环境与约束:...
- 角色与权限:...
- 初始条件与测试数据:...
- 外部依赖:...
- 完成后的状态与清理:...

## 场景

| ID | Scenario | Given / When / Then | Type | Priority | Status | Evidence |
|---|---|---|---|---|---|---|
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add jimyag/dotfiles/test-scenarios@sha256:5bd669219b000d1a

The line at the top of this page pins the label git:20261015.f79eac0, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_jqwwjzpn5qqfy356.svg)](https://markdownregistry.com/a/art_jqwwjzpn5qqfy356)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 6 versions of this file, between Sep 18, 2026 and Oct 15, 2026, about one every 5 days.

versioncommittedcommitsizeaudit
git:20261015.f79eac0 latest2026-10-15 f79eac0 12,090 BA view · diff
git:20260929.603248c2026-09-29 603248c 11,166 BA view · diff
git:20260927.a7267d02026-09-27 a7267d0 11,007 BA view · diff
git:20260920.878daed2026-09-20 878daed 11,011 BA view · diff
git:20260919.361331b2026-09-19 361331b 11,011 BA view · diff
git:20260918.f8de0f42026-09-18 f8de0f4 9,578 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (12090 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

GitHub

jimyag/dotfiles · 11 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jqwwjzpn5qqfy356
GET https://markdownregistry.com/api/v1/resolve?ref=jimyag/dotfiles/test-scenarios
GET https://markdownregistry.com/api/v1/blob/5bd669219b000d1a11d745354fdf49ddf58d1ee0f4c7a60d4a37f9a0723bc819

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.

More from jimyag/dotfiles

absorb-skill SKILL.md skill
jimyag/dotfiles · skills/absorb-skill/SKILL.md · 用户想从外部技能生态寻找、比较可复用的 Agent Skill,或要求把外部 Skill、项目资料或历史经验中的可复用内容吸收到已有 Skill 时使用;对照来源与目标后修改目标…
git:20261019.0e15234 · audit B · 11 stars
agent-health SKILL.md skill
jimyag/dotfiles · skills/agent-health/SKILL.md · 在审计 AGENTS/CLAUDE 指令、MCP、hooks、工具权限、验证入口、跨工作流配置漂移,或技能库的规范、可移植性、触发重叠、上下文加载、脚本和评测时使用;不用于创建技能,不因普通任务涉及配置就触发。
git:20261019.0e15234 · audit B · 11 stars
architecture-decision-record SKILL.md skill
jimyag/dotfiles · skills/architecture-decision-record/SKILL.md · 已有具体技术决策,需要判断是否记录 ADR,或创建、更新、替代 ADR 时使用。
git:20260905.751659e · audit A · 11 stars
brainstorming SKILL.md skill
jimyag/dotfiles · skills/brainstorming/SKILL.md · 在目标、范围或成功标准不清,存在接近的实现方案,或高成本假设可能导致返工时使用;用户要求拷问、追问或 grill 方案时也使用。适用于实现前澄清需求、挑战隐含前提并收敛到一个推荐方案;不用于已经明确的小改动。
git:20261015.bb74506 · audit A · 11 stars
codecov-coverage SKILL.md skill
jimyag/dotfiles · skills/codecov-coverage/SKILL.md · 在需要查询 Codecov 仓库、PR、提交、patch 或文件覆盖率,比较覆盖率变化,或诊断 codecov/project、codecov/patch 等覆盖率检查失败时使用。
git:20260905.751659e · audit A · 11 stars
frontend-design-review SKILL.md skill
jimyag/dotfiles · skills/frontend-design-review/SKILL.md · 在确定或审查前端页面、落地页、作品集和重新设计的视觉方向时使用;区分只读审查、方向建议和已授权实现,并用真实截图或渲染验证视觉结论。不用于纯业务逻辑、状态管理或已经有明确设计稿的机械实现。
git:20261015.b377f6b · audit A · 11 stars
gh-stack SKILL.md skill
jimyag/dotfiles · skills/gh-stack/SKILL.md · 使用 gh-stack GitHub CLI 扩展管理堆叠分支和拉取请求。适用于创建、推送、变基、同步、切换、查看、重组或合并相互依赖的 PR 链及堆叠差异。
v0.0.9 · audit A · 11 stars
linux-performance-analysis SKILL.md skill
jimyag/dotfiles · skills/linux-performance-analysis/SKILL.md · 诊断 Linux 主机或容器的缓慢、高负载、资源压力及网络性能异常,定位瓶颈与触发进程;不用于普通命令语法查询。
git:20260905.751659e · audit A · 11 stars
loop-on-ci SKILL.md skill
jimyag/dotfiles · skills/loop-on-ci/SKILL.md · 在已有 GitHub PR 需要持续观察 Actions 检查、读取失败作业日志、修复问题、重新运行并跟到全部检查变绿时使用。适用于围绕同一个 PR 反复验证,而不是一次性状态查询。
git:20261015.b377f6b · audit A · 11 stars
pull-request SKILL.md skill
jimyag/dotfiles · skills/pull-request/SKILL.md · 创建 GitHub PR、更新标题或正文、填写 PR 模板,或准备人工发布内容时使用;不用于代码审查和 CI 修复。
git:20260919.361331b · audit A · 11 stars
requesting-code-review SKILL.md skill
jimyag/dotfiles · skills/requesting-code-review/SKILL.md · 用户要求审查当前代码差异或 PR 时使用,默认只读;不用于处理已收到的评审意见。
git:20261019.0e15234 · audit A · 11 stars
runtime-verification SKILL.md skill
jimyag/dotfiles · skills/runtime-verification/SKILL.md · 在提交或交付非平凡代码改动前,需要确认改动在真实运行面上按预期工作时使用;通过 CLI、接口、界面、公开包入口或代理行为驱动改动路径并留存证据。只改测试、文档或无运行面的类型声明时不触发;定位缺陷使用…
git:20261015.2c8093f · audit A · 11 stars

Every file in jimyag/dotfiles

Browse by kind, by grade A, or by owner.