zer0-mistakes

Run ONE incremental pass of the zer0-mistakes issue autopilot — analyze open issues, group them into batches, then route/triage them (apply area:*/priority:* labels, flag stale bot-noise, decompose epics, leave backlog-synced issues alone) or resolve one docs batch into a single grouped PR. Use when asked to triage issues, work the issue queue, run the issue-autopilot loop, or drive the issue-triager / issue-resolver agents.

Build, launch, serve, and screenshot the zer0-mistakes Jekyll theme site locally. Use when asked to run/start/serve/preview the site or theme, take a screenshot of a page, smoke-test routes, or confirm a layout/include/sass change renders in the real running site (not just tests). Drives the live Jekyll server at localhost:4000 with a headless Chromium driver.

**WORKFLOW SKILL** — The standard branch → commit → PR flow for ANY change to Zer0-Mistakes. USE FOR: starting any code/content/docs/config change, deciding how to split mixed work, naming branches/commits, keeping generated & lock files out of feature PRs, opening a PR correctly so release tooling computes the right version bump. INVOKES: git (switch/worktree/add/commit/push), gh pr create, and the validate-build skill. DO NOT USE FOR: cutting an actual release (use the commit-publish prompt) or pure read-only investigation.

**WORKFLOW SKILL** — How the /issue-plan committee fans out four read-only lenses over the open backlog and synthesizes an ORDER-ONLY plan deterministically. USE WHEN running /issue-plan or building the planning step. INVOKES: the plan-lens-* agents (or inline personas), scripts/sync-plan.rb. DO NOT USE FOR implementing tasks (use /issue-implement) or filing them (use /repo-audit intake).

**WORKFLOW SKILL** — Review new/changed Jekyll content (Markdown under pages/**) for SEO, consistency, polish, accessibility, and technical accuracy, using PER-COLLECTION thresholds. USE FOR: reviewing a content PR before merge, auditing a post/doc/quickstart/note you just wrote, pre-publish SEO + style checks, resolving AI-content-review feedback. INVOKES: scripts/content-review.rb (deterministic tier), the content-reviewer Claude Code agent, .github/config/content_review.yml, the per-collection .github/instructions/*.instructions.md. DO NOT USE FOR: code/theme review (use /code-review), bulk front-matter-only normalization (use /frontmatter-maintainer), or releases (use commit-publish).

**WORKFLOW SKILL** — Read, draft, and post the GitHub Discussions that back the site's Giscus comment threads, so Claude Code can build conversations from page comments. USE FOR: reading the comment thread on a page, summarizing reader feedback, drafting a maintainer reply, replying to a specific comment, or seeding a discussion for a page that has none yet. INVOKES: scripts/bin/giscus-discussions (gh GraphQL engine), _config.yml (giscus.* config), pages/_docs/features/giscus-comments.md. DO NOT USE FOR: enabling/configuring the widget (edit _config.yml + see the feature doc), code/theme review (use /code-review), or content editing (use /content-review).

**WORKFLOW SKILL** — The standard for proving a UI/behavioural change works: a regression test + before/after visual evidence, attached to the PR and surfaced in release notes. USE FOR: any change under _sass/ _includes/ _layouts/ assets/ (or any user-visible behaviour); after a bug fix that changed rendering; before adding the `auto-merge` label to a fix. INVOKES: test/visual/evidence-kit.mjs, Playwright, the validate-build skill. DO NOT USE FOR: pure docs/data/config edits with no visual or behavioural effect (label the PR `skip-evidence`).

**WORKFLOW SKILL** — Validate a Zer0-Mistakes change before commit/release. USE FOR: pre-commit checks, pre-PR verification, debugging a broken build, confirming theme/include/layout/Sass/Obsidian changes work end-to-end, smoke-testing the gem, reproducing CI failures locally. INVOKES: docker-compose, bundle exec jekyll, yamllint, markdownlint, the project test runners under test/. DO NOT USE FOR: actual releases (use the commit-publish prompt) or one-off `jekyll build` invocations where you already know what to run.