From apex
Generate tests for a specific crate or file, targeting uncovered branches.
npx claudepluginhub sahajamoth/apex --plugin apexGenerate tests for a specific crate or file, targeting uncovered branches. ``` /apex-generate <crate-or-file> ``` Examples: - `/apex-generate apex-coverage` — generate tests for the oracle - `/apex-generate apex-fuzz/src/mutators.rs` — generate tests for mutators - `/apex-generate apex-agent` — generate tests for the agent orchestrator 1. Identify the target from `$ARGUMENTS` (required — ask if...
Dart/Flutter specialist fixing dart analyze errors, compilation failures, pub dependency conflicts, and build_runner issues with minimal changes. Delegate for Dart/Flutter build failures.
Accessibility Architect for WCAG 2.2 compliance on web and native platforms. Delegate for designing accessible UI components, design systems, or auditing code for POUR principles.
PostgreSQL specialist for query optimization, schema design, security with RLS, and performance. Incorporates Supabase best practices. Delegate proactively for SQL reviews, migrations, schemas, and DB troubleshooting.
Generate tests for a specific crate or file, targeting uncovered branches.
/apex-generate <crate-or-file>
Examples:
/apex-generate apex-coverage — generate tests for the oracle/apex-generate apex-fuzz/src/mutators.rs — generate tests for mutators/apex-generate apex-agent — generate tests for the agent orchestratorIdentify the target from $ARGUMENTS (required — ask if missing).
Read the source file completely to understand:
#[cfg(test)] blocksRun cargo llvm-cov --json to find uncovered regions in the target file.
Write tests that cover the uncovered regions. Place them in:
#[cfg(test)] mod tests { ... } inside the source file, ORcrates/<name>/tests/<module>_tests.rs for integration testsRun cargo test -p <crate> to verify they pass.
Report: which regions are now covered, new coverage %, and any remaining gaps.
#[tokio::test] for async functionsBranchId values directly