jadenfix

High-recall, high-precision independent review of a beater.js PR. Use when asked to review a PR in jadenfix/beater.js (e.g. "/review-pr 110"), especially for docs/contracts, test gates, systems-engineering decisions, security boundaries, performance claims,…

Select and run beater.js verification gates on this local macOS workspace, including docs-only checks, focused Cargo tests, npm/node compatibility, LLM provider conformance, browser/provider gates, deploy gates, CI queue checks, and the PyO3 configuration…

Keep beater.js documentation, public contracts, final.md evidence, OpenAPI/action metadata, and ecosystem-facing scope honest. Use when changing routes, status codes, schemas, MCP/tool/action surfaces, build/deploy behavior, docs, milestones, or completion…

Make high-leverage beater.js architecture, language, framework, algorithm, performance, reliability, and security decisions. Use when choosing an implementation approach, optimizing a hot path, refactoring, selecting Rust/TypeScript/Python/C++/Wasm…

End-to-end documentation and scope iteration for jadenfix/aether. Use when writing, reviewing, or finalizing README sections, ecosystem docs, architecture docs, PR bodies, roadmaps, specs, public contracts, generated-client-facing docs, or any doc cleanup…

High-recall, high-precision independent review of an aether PR. Use when asked to review a PR in jadenfix/aether (e.g. "/review-pr 400"). Reviews must be done by an agent that did NOT author the PR.

Rigorous systems engineering and technology selection for jadenfix/aether. Use when choosing architecture, language, framework, algorithm, data model, runtime, protocol boundary, optimization strategy, or security/resource-control design, especially when the…

Language, framework, library, runtime, data-structure, and algorithm selection for jadenfix/aether. Use when choosing what technology or algorithm to use, replacing an existing approach, optimizing for performance or adoption, or deciding whether a new…

Design and review beaterOS systems work for close-to-metal performance, security, and macOS compatibility. Use when changing architecture docs, Rust/C/assembly boundaries, kernel/runtime contracts, sandboxes, schedulers, journals, receipts, model/tool/payment…

Run beaterOS review gates for PRs that change runtime contracts, infra gates, docs, and migration evidence.

High-recall, high-precision independent review of a beaterOS PR. Use when asked to review a PR in jadenfix/beaterOS (e.g. "/review-pr 106"). Reviews must be done by an agent that did NOT author the PR.

Merge a GitHub PR via squash after /preparepr. Use when asked to merge a ready PR. Do not push to main or modify code. Ensure the PR ends in MERGED state and clean up worktrees after success.

Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /reviewpr. Never merge or push to main.

High-recall, high-precision independent review of a tempo PR. Use when asked to review a PR in jadenfix/tempo (e.g. "/review-pr 217"). Reviews must be done by an agent that did NOT author the PR.

Repeatable GitHub cleanup workflow for jadenfix/tempo. Use when asked to resolve all Tempo GitHub PRs/issues, merge eligible PRs, triage or close issues, keep work isolated in git worktrees, and prove fixes with current-main merge checks plus e2e or…

High-recall, high-precision independent review of a beatbox PR. Use when asked to review a PR in jadenfix/beatbox (e.g. "/review-pr 28"). Reviews must be done by an agent that did NOT author the PR.

High-recall, high-precision independent review of a beater-memory PR. Use when asked to review a PR in jadenfix/beater-memory (e.g. "/review-pr 45"). Reviews must be done by an agent that did NOT author the PR.