all publishers

zaxbysauce

@zaxbysauce source repo

208 published skills · page 3 of 3

  1. ▌
    Closeout Remote · zaxbysauce
    End-of-session knowledge closeout for sessions WITHOUT access to the zmem store — cloud sessions, Claude Code Remote (CCR), or any other machine that cannot reach this box's store.py. Reflects on the session with the same capture bar as the local `closeout` skill, then emits a portable JSON harvest instead of writing to the store directly. Use when the user says "closeout", "wrap up", "end of session", "capture what we learned" in a session that has no local zmem store, or when `store.py`/`ZMEM_DATA` is unreachable. Pair with the `/ingest-harvest` command, run later on a machine that does have the store, to actually write the results.
    528 repo stars
  2. ▌
    Swarm · zaxbysauce
    Enable a high-quality swarm-like Claude Code workflow for the current session, and optionally execute a task immediately using that mode. Uses parallel subagents for breadth, independent reviewer validation for precision, and critic challenge for final confidence. Use when the user wants swarm-like behavior, higher review rigor, or maximum quality without sacrificing Claude Code speed.
    528 repo stars
  3. ▌
    Contributing · zaxbysauce
    End-to-end PR workflow for opencode-swarm. Covers branch setup, conventional commits, mandatory release notes, 5-tier CI checks, and PR submission format. Load this skill before creating branches, commits, or pull requests.
    528 repo stars
  4. ▌
    QA Sweep · zaxbysauce
    Apply when implementing features, fixing bugs, debugging errors, investigating failures, tracing root causes, reviewing tech debt, tracing issues, planning fixes, or completing any task. Enforces parallel sub-agent implementation, independent adversarial review, and a 95% confidence gate before stopping.
    528 repo stars
  5. ▌
    Commit Pr · zaxbysauce
    Apply when committing, pushing, opening a PR, writing a pull request, creating release notes, or updating a changelog. Enforces conventional commit format, mandatory release notes, 5-tier test suite, SHA-pinning for workflow changes, and correct PR body format.
    528 repo stars
  6. ▌
    Writing Tests · zaxbysauce
    Apply when writing tests, modifying test files, fixing test failures, debugging CI failures, adding test coverage, creating adversarial tests, or reviewing any file under tests/. Also apply when implementing features or fixes that require corresponding test changes. Enforces bun:test framework rules, mock isolation, cross-platform compatibility (Linux, macOS, Windows), and CI pipeline awareness. Load this skill before touching any test file.
    528 repo stars
  7. ▌
    Research First · zaxbysauce
    Apply when planning fixes, investigating tech debt, architecting solutions, or diagnosing unknown issues. Search online for current documentation and state-of-the-art approaches before tracing through code.
    528 repo stars
  8. ▌
    Tech Debt CI Review · zaxbysauce
    Deep technical debt and CI stability audit for identifying test theater, missing or mis-scoped tests, actual and potential test failures, flaky-test risk, dependency/toolchain brittleness, and structural debt that prevents PRs from going green safely.
    528 repo stars