跳到正文
cccskills
免费在 GitHub 公开

gentle-ai-bench

Create and verify gentle-ai journeys, which are scripted sequences of product actions. Check their declarations separately from actual execution, review outdated expectations after behavior changes, and record execution results for pull requests.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.

查看安装方法

适用场景

  • Adding a product operation journey
  • Updating expectations after behavior changes
  • Reproducing a bench failure from CI
  • Preparing journey execution evidence for a pull request

包含的文件(1)

  • SKILL.md3.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Activation Contract

Load when touching bench/ in gentle-ai, adding or changing a journey, changing a product semantic a journey might pin, or diagnosing a bench failure in CI's Unit Tests job.

Hard Rules

  • go test ./bench validates corpus declarations only. It does NOT execute journeys. The only driven proof is building the harness and the product binary and running the harness against it; a green go test ./bench claims nothing about execution.
  • Reproduce CI, do not guess invocations: read the Unit Tests step in .github/workflows/ci.yml and copy its exact build and gentle-ai-bench run --binary ... commands. Use --only <journey-id> to drive one journey.
  • Journey IDs are unique across every journeys_*.go file. The collision guard fails loudly naming both files; pick an unused ID by reading the corpus, never reuse a retired one.
  • Every journey declares Review: — reviewOptedIn (the runner enables receipt-driven development globally before the first step, uncounted, and fails the journey if the switch does not come on) or reviewUntouched (its subject IS the switch, or it has nothing to do with reviews). The declaration is mandatory; validateCorpus fails the run without it. Lifecycle journeys must not depend on the product default. Reviews default to ON; reviewUntouched does not imply OFF. Journeys requiring OFF must explicitly disable it, while default-mode journeys must assert ON/default with unset sources.
  • Every execute transition must carry a runnable command; the dead-execute guard fails the run otherwise.
  • When a ratified product semantic changes, grep the corpus for journeys pinning the OLD behavior before shipping. The corpus is a second test surface beyond unit tests; a journey asserting the defect keeps the defect green.
  • dead_end prints n/a unless the run actually measured one. Never fabricate a value to move the column.
  • A by_design exemption costs a shape from the closed vocabulary plus a verified quote of the product's own next-action text. If the quote no longer tells the operator what to do, it is a defect wearing an exemption.
  • Prefer a NEW journeys_*.go file when the shared ones are owned by open PRs; bump the core journey-count pin in the same change.

Execution Steps

  1. Read the corpus area you touch and the CI invocation before writing.
  2. Author or adapt the journey; update its title, step names, and comment to say WHY the expectation holds (cite the issue or ratified decision).
  3. Run go test ./... in bench/ for declarations, THEN the driven harness for execution; both results go in the PR body.
  4. On semantic changes, list the journeys you checked for stale pins.

Output Contract

PR evidence includes the driven-mode summary line (completed / unsupported / failed counts) from a locally built binary, not only go test output.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

branch-pr

免费

Prepare pull requests by checking approved issue links, change-type labels, and required automated checks. Draft the repository’s PR template using observed test results, while leaving commits, pushes, PR creation, and merging under human control.

中文简介正在准备中。当前显示英语简介。

  • Preparing a branch for review
  • Drafting a PR linked to an approved issue
  • Checking required CI before declaring a PR merge-ready
Gentleman-Programming/gentle-ai79392026年10月22日 更新

Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.

中文简介正在准备中。当前显示英语简介。

  • Splitting a change that exceeds 400 lines
  • Planning PRs that can merge independently
  • Coordinating a feature through a draft tracker PR
Gentleman-Programming/gentle-ai79392026年10月22日 更新

Structure guides, READMEs, design documents, and pull request descriptions so readers can find answers quickly. Put outcomes first, introduce details gradually, and use examples, tables, and checklists to support understanding and review.

中文简介正在准备中。当前显示英语简介。

  • Reorganizing a long or dense README
  • Writing an onboarding guide for new contributors
  • Making a pull request's review steps clear
Gentleman-Programming/gentle-ai79392026年10月22日 更新

Draft clear, considerate comments for code reviews, issue replies, and team updates. Put the actionable point first, explain technical reasons when needed, and give a concrete next step while matching the conversation’s language.

中文简介正在准备中。当前显示英语简介。

  • Requesting a code change with a clear reason
  • Replying to a contributor’s issue
  • Writing a brief asynchronous team update
Gentleman-Programming/gentle-ai79392026年10月22日 更新

Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.

中文简介正在准备中。当前显示英语简介。

  • Preparing a branch for a fix or feature
  • Drafting a pull request linked to an approved issue
  • Organizing test results and reviewer notes
Gentleman-Programming/gentle-ai79392026年10月22日 更新

Split large code changes into linked pull requests, each with a focused scope. Organize their order, dependencies, and verification steps so reviewers can assess one unit of work at a time.

中文简介正在准备中。当前显示英语简介。

  • Splitting a pull request with more than 400 changed lines
  • Planning the review order for dependent changes
  • Integrating a feature through a shared branch
Gentleman-Programming/gentle-ai79392026年10月22日 更新

查看 Gentleman-Programming 的全部技能

报告此技能的问题