(t *testing.T)
| 549 | "## 1a. When invoked explicitly with no intent", |
| 550 | "DO NOT auto-run any workflow", |
| 551 | "do not enter §4.1", |
| 552 | `What now?`, |
| 553 | "Just exploring", |
| 554 | } { |
| 555 | if !strings.Contains(got, want) { |
| 556 | t.Errorf("skill missing §1a content: %q", want) |
| 557 | } |
| 558 | } |
| 559 | } |
| 560 | |
| 561 | // TestSkillNoCliCoachingInUserFacingLabels pins the rule that the |
| 562 | // skill must not put literal `flow ...` invocations inside |
| 563 | // AskUserQuestion option labels or chat replies. Users should never |
| 564 | // see CLI commands; Claude uses flow under the hood. |
| 565 | // |
| 566 | // We pin two specific past offenders that motivated the sweep — the |
| 567 | // "Run init?" prompt that read "Yes, run flow init", and the |
| 568 | // "Mark done?" prompt that read "Yes, `flow done <slug>`". If either |
nothing calls this directly
no outgoing calls
no test coverage detected