skills

Manual E2E tester that starts the app and exercises new features end-to-end

Generate a single self-contained HTML page that is genuinely visual AND interactive — charts, diagrams, motion, tabs, comparison toggles, click-to-expand, base64-inlined images, opinionated typography. Use whenever the user wants ANY rich visual artifact from arbitrary content: explainer, research write-up, PRD or spec page, pitch, internal one-pager, "make this less boring" rebuild, scroll-snap deck, landing-style summary, distilled report. Trigger phrasings: "make me a page about X", "turn this PDF/doc into something visual", "build me a deck/talk/pitch", "explain Y in a visual way", "make this readable", "give it some eye candy", "I want something I can show the team", "less boring version of this", "rebuild that page", "redo it with more visuals". Output is one .html file that renders identically when DM'd — CDN libraries (Tailwind, Chart.js, D3, GSAP, Mermaid, Lucide) load from stable jsdelivr/unpkg URLs; every image is base64-inlined. Not for plain Markdown docs (use technical-writer), not for code revi

Vision-based visual QA reviewer — captures rendered output (live web pages, static HTML artifacts, PDFs) as screenshots, inspects them with a designer's eye for layout defects a human catches instantly, and normalizes findings into the verify pipeline format

Independent second-opinion reviewer that shells out to the local Codex CLI for a broad code review, then normalizes findings into the verify pipeline format

Comment-hygiene-only reviewer — flags ephemeral review-ID references, historical change-narration, stale comments, reviewer-appeasement, and redundant restating in the scoped diff, and normalizes findings into the verify pipeline format

Adversarial cooperation loop — player implements, /verify reviews, creates PR, passes CI

Comprehensive code reviewer combining design review, architecture, coherence, hardening, and security analysis

Run comprehensive triage-first verification pipeline with specialized skills. Detects scope, discovers toolchain, triages files to relevant skills, runs static analysis, invokes review skills in parallel, exercises the app, and produces a unified report. Supports interactive, report-only, and auto-fix modes.

Implementation skill for player-coach. Reads the plan, writes code and tests, and addresses verification feedback.

Pragmatic QA engineer that evaluates test coverage quality, flags untested changes, and assesses whether tests provide real confidence — adapts expectations to codebase testing maturity

Adversarial review coach for root cause analysis. Reviews reports with fresh eyes, runs verification commands to spot-check evidence claims, pushes hard on depth and rigor.

Static analysis runner that executes pre-discovered linter and type-checker commands on scoped files and reports findings

No-nonsense test executor that reports failures without attempting fixes

User experience specialist that evaluates all user-facing outputs for clarity and usability

Reconcile this repository toward the opinionated "golden state" for agentic local development — a per-repo dev CLI, a thin justfile surface, a generated port-offset env contract, a four-file engineer skill, thin CI, and a doctor invariant-enforcer. Run /setup-engineer whenever you want to set up, audit, or repair a repo's local-dev tooling: a fresh repo with nothing, a half-built repo with organic scripts that needs consolidating, or a finished repo you just want to verify still conforms.

Multi-source research specialist that investigates a topic, verifies claims across independent sources, and reports findings with dated citations. Use this whenever the user wants you to research, investigate, "look into", "dig into", "find out about", "get up to speed on", or "what's the latest on" something; to compare options ("X vs Y", "which is better"); or to map a landscape ("give me the lay of the land on Z"). Two depths: a normal request gives a fast cited report in chat; saying "deep research" (or passing --deep) runs a multi-phase investigation that fans out parallel sub-agents across the branches of the topic, synthesises them, and renders the result as a rich visual HTML page via the rich-page skill. Prefer this skill over answering research questions from memory — it verifies and cites instead of guessing. Not for reviewing code, summarising a single document you already have, or debugging a specific failure (use reviewer / technical-writer / debugger for those).

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Create a pull request or merge request with rich, context-aware description and inline review comments. Analyzes changes to explain what changed, why, and where reviewers should focus attention. Handles branch creation, commits, push, platform detection (GitHub/GitLab), and label assignment. Use this skill whenever creating a PR/MR, even for simple changes — it always produces better descriptions than a manual `gh pr create`. Accepts optional context from callers like player-coach for even richer descriptions with implementation journey and friction logs.

Summarize all changes in current branch compared to base branch

Document current plan and progress into handoff file

Filter and curate a KubeCon schedule from ICS calendar exports. Parses the raw schedule, applies heuristic filters to surface deep dives and high-signal talks, then iteratively refines recommendations based on user feedback. Outputs a curated markdown list and a filtered ICS file. Use this skill whenever the user mentions KubeCon schedule, KubeCon talks, filtering conference sessions, or wants help deciding which KubeCon sessions to attend — even if they just say "help me pick talks" or "there are too many sessions."

Root cause analysis — investigate directly in main context, then invoke a coach skill for adversarial review

Monitor CI/CD pipeline status after pushes and investigate failures.

Evidence-based troubleshooting specialist that analyzes problems without fixing them

Generate user-facing release notes from technical change information (commits, PRs, diffs, branch comparisons, or raw text). Goes deep — follows commit references to PRs, issues, and bug reports to understand the full story behind each change, then produces narrative prose that communicates what changed and why it matters. Works with GitHub, GitLab, and Jira. Use this skill whenever the user asks for release notes, changelogs, "what's new" summaries, or wants to communicate changes to users, stakeholders, or customers — even if they just say "write up what changed" or "summarize the release."

Review a pull/merge request by fetching PR details, checking CI, and running verification skills on the changes

Expert technical documentation editor following Google and Grafana style guides for clear, developer-focused content