zucca-skills

Use when you need to merge a batch of related PRs (a feature-spec-keeper run, a coverage-keeper run, a docs-bot run, etc.) where each merge triggers conflicts on append-only log files in the others. The skill resolves the merge-rebase-merge cascade automatically, surfaces blockers, and stops on any unrecoverable conflict. Triggers on "merge all the X PRs", "merge this batch", "merge every coverage-keeper PR", or any "we have N related open PRs, merge them in order" flavor of request.

Use when CI is failing because Neon's create-branch action returns HTTP 422 (rate-limited at concurrent branch creation, or near a project quota) or when stale preview / CI / dev-local branches have piled up in a Neon project. The skill lists branches, filters by age + creation source + protection state, shows the user the deletion candidates for confirmation, and deletes in batches via the Neon MCP. Triggers on "prune Neon branches", "clean up Neon", "delete old previews on Neon", "Neon is at quota", or any "CI is failing on create-branch" investigation.

Use when one or more open PRs are blocked on transient CI failures — typically `db-data-integrity` / `db-schema-integrity` flapping on Neon rate-limits, `promptfoo-eval` flaking on LLM rate-limits, or `e2e` cascade-failing because preview-env Clerk auth hiccupped. The skill identifies the latest FAILED run for each named check across a PR list, reruns just those failed jobs (not whole workflows), surfaces persistent failures so they get human attention, and stops cleanly. Triggers on "rerun the failed checks", "retry CI on these PRs", "rerun any failed promptfoo", "the db checks are flaking again", or any "CI flake retry on a batch" request.

Use when a feature-spec-keeper (or similar reverse-engineering agent) opens a batch of spec PRs with `## Open questions for the rewrite` sections that need human answers before merge. The skill groups questions, applies the team's status-quo-for-features-fix-bad-architecture policy as default recommendations, walks PRs one at a time, captures answers, patches the spec doc, and pushes. Triggers on "walk the open questions on this PR", "answer the spec questions in batch", "let's resolve feature-spec PRs one by one", or any "I have N spec PRs with open questions, help me work through them" request.