adamayoung

Build the project for testing

Build the project

Take the current plan all the way to a ready-to-merge pull request — review the plan (scaled to risk), implement it test-first, code-review and fix, security-review, verify the acceptance criteria, open the PR, and watch it green. Use after you have an approved plan (e.g. from plan mode) and want the rest of the feature pipeline run end-to-end. Invoking it is itself plan approval — it then runs autonomously to a single hard stop: ready-to-merge.

Run a specific test target or test class

Run all unit tests

Run snapshot tests

Capture durable, project-specific learnings from the work just done into the knowledge/ base — gotchas, implementation quirks, tooling traps, SwiftData/CloudKit & TMDb-mapping surprises, things looked up or web-searched, and design decisions (as ADRs). Use before opening a PR (it runs automatically in /deliver), or any time you've learned something worth remembering. Records only non-obvious, reusable facts; skips anything already in the repo, CLAUDE.md, or git history.

Create a pull request

Take the current plan all the way to a ready-to-merge pull request — review the plan (scaled to risk), implement it test-first, code-review and fix, run the CI gate, open the PR, and watch it green. Use after you have an approved plan (e.g. from /plan) and want the rest of the feature pipeline run end-to-end. Invoking it is itself plan approval — it then runs autonomously to a single hard stop: ready-to-merge.

Diagnose and fix a failing scheduled (or standalone) TMDb Integration workflow run — re-run transients, or fix real drift on a branch off main, then PR and (optionally) merge. Use for the weekly Sunday Integration cron failure, or any red Integration run not tied to an open PR.

Review the working-tree changes (vs main) for correctness, concurrency, architecture, testing, and API/doc issues — following .github/CODE_REVIEW.md — and return a severity-graded report. Scales the machinery to the diff size: a single code-reviewer agent for a small change, or a fan-out-and-verify Workflow for a large/multi-unit one. Produces findings; it does not apply fixes (the caller does).

Watch the current branch's PR — reply to and resolve review threads, fix failing checks, and optionally merge when ready

Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors. Use after changing tests or shared code to check everything still builds — delegates to the tooling-runner agent (Haiku) and returns a concise pass/fail + errors-as-file:line summary. Differs from /build, which compiles only the library; to run the tests, use /test.

Compile the TMDb Swift package for the current platform to check it builds. Use to verify code compiles after changes — delegates the build to the tooling-runner agent (Haiku) and returns a concise pass/fail + errors-as-file:line summary, keeping logs out of context. To also compile the test targets, use /build-for-testing.

Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat failure), apply and verify the fix, commit, and push once — then return a summary. Use standalone when CI is red, or as the check-fixing step invoked by /watch-pr. Repo is adamayoung/TMDb.

Run the TMDb integration tests against the live TMDb API (the Integration test plan; requires TMDB_API_KEY/USERNAME/PASSWORD). Use before a PR, or after model/fixture changes, to validate against real API responses — delegates to the tooling-runner agent (Haiku) and returns counts + failures, distinguishing genuine failures from transient live-API/env issues. For mocked unit tests, use /test.

The canonical guide to Adam's writing voice and the de-AI lint that enforces it — British spelling, direct second person, no em-dashes, a delete-on-sight list of AI tells, and sentence-rhythm rules. Use it whenever you write or polish prose meant to sound like Adam (blog posts, READMEs, talk abstracts, release notes, LinkedIn posts, emails), and run its checks before showing him anything. blog-post-writer composes this skill. Triggers: "make this sound like Adam", "de-AI this", "check the voice", "run the AI-tell lint", "/adam-voice".

Use this skill to create or refresh the visual assets for a blog post on adam-young.co.uk — the wide hero, the square thumbnail, and any in-body diagrams. It produces on-brand SVG sources and rasterizes the committed PNG exports. Use it when writing a new post (invoked by blog-post-writer) or on its own to redo art for an existing post. Triggers: "make the hero image", "regenerate the thumbnail", "redo the art for <post>", "the hero looks same-y", "/blog-post-images".

Use this skill when Adam wants to write a blog post for adam-young.co.uk. He will usually hand over a PDF of a talk, a draft transcript, or rough notes. The skill structures the source content into a finished post in his voice, picks tags, and delegates the hero/thumbnail art to the blog-post-images skill. It does NOT invent ideas, opinions, examples, or facts that aren't in the source. Triggers: "write a blog post", "draft a post", "turn this PDF/talk into a blog post", "blog this", "/blog-post-writer".

Review a draft blog post for adam-young.co.uk from two independent angles — a Staff iOS engineer (senior-credibility) and a mid-level iOS engineer (does-this-teach) — and return one merged, deduplicated report. Use when Adam wants a substance/audience review of a post before publishing, after blog-post-writer has drafted it. Triggers: "review this post", "review the blog post", "get the reviewers on it", "/review-blog-post".