Auto-approved commit, push, CI monitor, and deploy to production
Auto-approved commit, push, and deploy to production — skips the CI/Security gate for fast, locally-verified deploys. Classifies what changed and deploys the Vue app and/or the Astro marketing site as needed (same target-classification as deploy-prod-auto, minus the remote-CI wait).
Turn a scattered, half-formed idea, bug report, or feature request into a complete, well-researched row in the "Beanies Main Issue Tracker" Notion DB — researching the codebase, recent commits, docs, and the web to fill every field, asking only about genuine gaps, checking for duplicates, showing the full proposed issue for approval, and then creating it as a "Not started" row that /beanies-pre-plan can pick up. Use this WHENEVER the user wants to capture, log, file, raise, open, add, or jot down an issue / bug / feature / idea / ticket / tracker item / TODO for beanies — even when they just describe a problem or wish ("the calendar feels cramped on mobile", "we should let users export their data", "remember to fix the flaky sync toast") without saying the word "issue". It is the front door to the tracker and the step BEFORE /beanies-pre-plan.
Standardized requirements-intake step that runs BEFORE beanies-plan. Collects complete, well-structured intent (via a copy/paste template or a Notion issue row), reviews EVERY field, asks the user to resolve anything missing/unclear/TBC (writing resolved values back to the tracker) before building, and — when a mockup is requested — generates a CIG-clamped UI mockup via the frontend-design skill, gets it approved, and stores it on the tracker. Only after explicit user approval does it hand a fully-populated initial prompt (plus any approved mockup) to beanies-plan. Use when the user says "pre-plan this", "intake this issue", "prep a plan for X", or invokes /beanies-pre-plan.
Create standardized plans (and optionally GitHub issues) using a mandatory 4-pass review discipline — initial draft, DRY/error-handling, sustainability/maintainability, and fresh-eyes final sweep — with full context preservation.
Review, prepare and publish a beanies.family "beanstalk" blog post that lives in the Notion Blog Posts database. Use this skill whenever greg mentions the blog, the beanstalk, a Friday post, publishing or reviewing a post, a post ID or Notion blog row, blog images, Substack cross-posting, or says anything like "it's blog day", "review my post", "is post 12 ready", "ship the blog", or "time for this week's post" — even if he doesn't name the skill. Also use it when asked to check a draft's tone, grammar, SEO, or images before publication, or to sync a Notion post into the repo.
Diagnose and fix failing Playwright E2E tests end-to-end — pull the failing CI logs (the `E2E Tests` GitHub Actions workflow), correlate against recent commits, decide whether each failure is a real product bug / test drift / flake, apply a structural fix, cull or consolidate tests that violate ADR-007, then run and re-run until every browser is green. Use whenever greg says the e2e tests are red/broken/failing, asks to fix or investigate E2E or Playwright failures, mentions a failing `E2E —` CI job or the `run-e2e` label, pastes a Playwright failure, or invokes `/fix-e2e-tests` — especially after development work, since that's when E2E breaks most.
Create, review, and maintain beanies.family Help Center articles — how-to guides, explainers, and reference docs