Skip to content
cccskills
FreePublished on GitHub

tdd

Apply Yuzu-specific test-driven development using tracer-bullet red-green-refactor cycles and the repo's Meson, gateway, proto, and ABI validation rules. Use when the user says `/tdd`, asks for TDD, red-green-refactor, or wants a feature/fix built test-first in Yuzu.

The English summary is being prepared. Showing the original description.

DevNullLtd/Yuzu
See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

TDD

Use behavior-first tests through public interfaces. Prefer integration-style seams that exercise real stores, REST handlers, gateway paths, plugin boundaries, or command dispatch contracts. Avoid tests coupled to private implementation.

Before Red

  • Read CONTEXT.md and relevant ADRs in docs/adr/.
  • Identify the public interface and the project term for the behavior.
  • List the smallest vertical behavior slice that proves value.
  • Choose the narrowest validation path through $yuzu-build.
  • Invoke $yuzu-proto, $yuzu-plugin-abi, $yuzu-meson, or $yuzu-windows-msvc if the slice crosses those boundaries.

Cycle

  1. Red: add one failing test for one observable behavior.
  2. Green: implement only enough code to pass that test.
  3. Verify: run the targeted suite with meson test -C <builddir> --suite <suite> --print-errorlogs or the relevant gateway command.
  4. Repeat for the next behavior.
  5. Refactor only while green.

Do not write all tests first. Use tracer bullets: one behavior, one test, one implementation.

Yuzu Test Hygiene

  • Use yuzu::test::unique_temp_path(prefix) or TempDbFile for C++ test temp files and SQLite DBs.
  • Avoid hardcoded shared paths and clock/thread-hash uniqueness.
  • For gateway EUnit, pass --dir apps/yuzu_gw/test.
  • For direct Erlang isolation, remove the relevant _build/test tree or run in a fresh BEAM.
  • For proto changes, include buf lint proto and buf breaking proto --against '.git#subdir=proto,ref=origin/main' when available.
  • For plugin ABI changes, add descriptor/loader coverage and preserve stable C ABI compatibility.

Done

Finish with the tests added, implementation green, targeted validation output summarized, and any broader /test --quick or governance follow-up called out.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adversarial-review

Free

Run an adversarial two-phase code review of a change with TWO independent reviewers — Claude and Codex — who review alone, then cross-examine each other's findings, then Claude synthesizes a single weighted verdict. Use when the user says "/adversarial-review", "adversarial review", "review this with Codex", "get Codex to review", "two-reviewer review", "cross-examine this PR", or wants a second independent model to grade a change before merge.

The English summary is being prepared. Showing the original description.

DevNullLtd/Yuzu19Updated Oct 19, 2026

auth-and-authz

Free

Authentication & Authorisation control plane for Yuzu — the canonical entry point for any work on RBAC, OIDC SSO, SAML, SCIM, MFA/TOTP, AD/Entra integration, API tokens, session lifecycle, enrollment, and the audit/evidence chain. Use when the user says "/auth-and-authz", "/auth", "/iam", asks to plan or implement an enterprise A&A feature, asks "what's our auth gap to enterprise readiness", asks to audit current auth state against SOC 2 CC6.x / Workstream B, or starts work that touches `auth_*`, `rbac_*`, `oidc_*`, `api_token_*`, `enrollment_*`, or `cert_store.*`. The skill bundles current-state inventory, required-features inventory, gap matrix, the canonical workflow for adding a new A&A feature, and the load order for the routed reference docs.

The English summary is being prepared. Showing the original description.

DevNullLtd/Yuzu19Updated Oct 19, 2026

ci-cache

Free

Canonical patterns for caching in Yuzu CI workflows. Two snippets — one for ephemeral GHA-hosted runners (split actions/cache/restore + actions/cache/save, never `save-always: true`) and one for self-hosted runners (local filesystem cache under `runner.tool_cache`, no GHA cache round-trip). Use when adding a new vcpkg/ccache/dependency cache step to any workflow under `.github/workflows/`, or when reviewing a PR that touches `actions/cache@`.

The English summary is being prepared. Showing the original description.

DevNullLtd/Yuzu19Updated Oct 19, 2026

cpp-expert

Free

Review Yuzu C++ source changes for C++23 correctness, idiomatic standard-library use, ABI boundaries, threading primitives, and cross-compiler portability across GCC, Clang, MSVC, and Apple Clang. Use for any governance Gate 3 review when `.cpp`, `.hpp`, or `.h` files change.

The English summary is being prepared. Showing the original description.

DevNullLtd/Yuzu19Updated Oct 19, 2026

cpp-safety

Free

Review Yuzu C++ source changes for resource ownership, RAII, borrowed lifetimes, C ABI contexts, casts, process/syscall boundaries, callbacks, threads, and sanitizer coverage. Use for any governance Gate 3 review when C++ files change, paired with cpp-expert.

The English summary is being prepared. Showing the original description.

DevNullLtd/Yuzu19Updated Oct 19, 2026

dev-team

Free

Run the current session as a senior developer (Opus) leading a configurable junior fleet. Decomposes requests into scoped tasks, dispatches junior-developer subagents in parallel, optionally runs an architect plan-review gate before dispatch, autonomously resolves escalations, optionally dispatches a doc-writer second wave after juniors complete, then integrates and gates with /test + /governance. Use when the user says "/dev-team", "run the dev team", "delegate this to the juniors", "act as the senior dev", or wants a task built by a senior-led fleet.

The English summary is being prepared. Showing the original description.

DevNullLtd/Yuzu19Updated Oct 19, 2026

See all skills by DevNullLtd

Report a problem with this skill