Use before/when investigating an OOM or memory blowup in a Polars pipeline job, or comparing candidate fixes/implementations by memory usage, or when asked to "add diagnostics", "instrument this job for memory", "profile this pipeline run". Documents how to…
Use when starting a new piece of work — "/new-ticket", "start a new ticket", "let's start on ticket 1234". Runs branch check → short interview → hands off to Plan Mode for the SPEC. Pairs with the `commit-push` and `open-pr` skills for the rest of the cycle.
Use when a ticket's work is ready for review — "/open-pr", "open a PR", "raise the PR". Run once, at the end of a ticket. Pairs with `new-ticket` and `commit-push`.
Use when writing a new unit test in this repo, or migrating an existing test off unittest. Encodes the repo's dataclass+parametrize pattern, naming conventions, mocking rules, and test-data storage rules from STYLEGUIDE.md.
Use when committing and pushing a chunk of work — "/commit-push", "commit and push this". Run repeatedly through a ticket, once per logical change, not just at the end. Pairs with `new-ticket` and `open-pr`.
Use when migrating a PySpark job or function in this repo (jobs/) to Polars (fargate/), or when asked to "migrate to polars", "convert this PySpark function", "port this job to fargate". Walks the repo's migration checklist so nothing from the PR template…
Use when reviewing a PR, diff, or set of changes within this repo — "review this PR", "review my changes", "code review". Encodes this repo's severity-tiered review structure and reviewer checklist, distinct from the generic built-in review/security-review…
Use when choosing or reviewing between a Polars .over() window function and a join-based rewrite (join_asof, group_by+join, semi/anti join) for streaming support or memory reasons. Triggers on ".over()", "window function", "join_asof", "streaming-friendly…