potiuk commented on code in PR #146: URL: https://github.com/apache/airflow-steward/pull/146#discussion_r3240728494
########## .claude/skills/issue-reproducer/probe-templates.md: ########## @@ -0,0 +1,174 @@ +<!-- SPDX-License-Identifier: Apache-2.0 + https://www.apache.org/licenses/LICENSE-2.0 --> + +# Probe templates — cross-family probes + +Companion to [`SKILL.md`](SKILL.md). Procedural detail for Step 9: +running a small probe across the family of types or operator +variants the reproducer's expression belongs to. + +## When to probe + +The probe pattern applies when the reproducer's central expression +exercises a behaviour that is **defined for multiple backing types +or via multiple operator variants** in the project's language / +runtime. + +Examples (project-dependent — define families per project in the +adopter override file or here): + +- **Type families.** A range/index expression in a language with + `List`, `Object[]`, primitive arrays, and `String` as + index-supporting backings. A path-navigation expression with + multiple backing models (in-memory graph vs lazy DOM vs streamed + source). +- **Operator-variant families.** Safe-navigation operators with + multiple variants (`?.`, `??.`, `?[..]`). Spread operators with + multiple variants. Comparison operators with multiple variants. + +When the reproducer's central expression is a member of such a +family, probe the rest of the family. The cost is small (~50-line +script); the signal is consistently useful — a project-wide spec +gap, an additional bug in a sibling type, or confirmation that +the asymmetry spans the whole operator family. + +## When NOT to probe + +Skip when: + +- The reproducer's expression isn't family-typed (a one-off + function call with no type-variant cousins). +- The probe would duplicate work already in the reporter's + multi-case reproducer (the reporter already covered the family). +- The user passed `--no-probe` (e.g., running through a campaign + where the campaign skill aggregates family analysis at a higher + level). + +## Probe template structure + +A probe is a single script that exercises the same expression +across every family member and emits a comparison table: + +```text Review Comment: ```suggestion ```groovy ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
