skylark

Use when reviewing the architecture & structure of Skylark code — a PR diff, the whole codebase, or one module. Hunts duplication, hard-to-test code, cleverness, deep nesting, files over 1k lines, weak seams (loose coupling + acyclic deps), and chances to do the same work in far fewer lines. Ambitious by design — for a crew with a high craft bar.

Use when writing or updating a zine — Skylark's spec format. Covers the required sections (tl;dr, Components, Structure, Decisions, Changelog) and the principles for what belongs in a zine versus a skill or elsewhere.

Use whenever an open PR needs shepherding to a merge — watching CI, weighing the agentic reviews, resolving merge conflicts, and merging once everything is green. Assumes the PR already exists (code is written, pushed, and `gh pr create` has run); this skill starts from there. Used by the `build-feature` skill's last step, and by any agent (e.g. a dedicated babysitter) whose job is watching a PR through to landing.

Use whenever building or changing a feature in Skylark — the loop from first failing test to an open, mergeable PR. Covers red-green TDD, making `npm run check` pass, committing on a branch, pushing, and opening a PR. Once the PR is open, hand off to the **babysit-pr** skill (or a dedicated babysitter agent) to shepherd it through CI, reviews, and the merge — a feature isn't shipped until that's done too.

Use when adding a new Skylark service — the native unit of data + logic + doors (web/CLI). Covers the folder shape, which deck it belongs in, wiring it to a view, testing it, and when to give it a zine.

Use when reviewing a PR's test quality via mutation testing. Runs Stryker on the diff, triages surviving mutants, and posts findings as a PR comment with inline annotations on changed lines.