Menú
Run test coverage analysis across Rust server, Kotlin Android app, and CLI. Identifies uncovered code and suggests where to add tests.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Push content to Boox e-ink tablet for iterative review. Supports multiple annotation rounds — user annotates, agent updates document via update_session tool, tablet reloads.
Render the eink WebView in local Chrome via DevTools MCP. Spawns a kitchen-sink or realistic-scenario session at the tablet viewport, optionally against a fresh `cargo run` server for iterating on `render.rs`. Includes a follow-up flow for verifying the same session on the actual Boox WebView via remote debugging.
Commit eink-bridge changes, bump the nix_dots flake input, and apply via nixos-rebuild. Use after editing skills, harness files, or server code in the eink-bridge repo.
Update the content of an active eink session on the Boox tablet. Use when iterating on a document mid-review without waiting for annotation events.
| name | coverage |
| description | Run test coverage analysis across Rust server, Kotlin Android app, and CLI. Identifies uncovered code and suggests where to add tests. |
Run coverage tools for the project's components and analyze gaps.
/coverage [component]
server or rust: Rust server + CLI only (cargo llvm-cov)android or kotlin: Android/Kotlin only (JaCoCo)config, session): focused coverage on that module.server/ directory:cd server && just coverage
# or directly:
cd server && nix develop .. --command cargo llvm-cov --text
Filename Lines Missed Cover
app.rs 252 7 97.2%
config.rs 76 17 77.6%
...
TOTAL 1425 101 92.9%
cd server && nix develop .. --command cargo llvm-cov --text --show-missing-lines
just coverage-android
# or directly:
cd android && nix-shell shell.nix --run './gradlew testDebugUnitTest jacocoTestReport'
The HTML report is at android/app/build/reports/jacoco/jacocoTestReport/html/index.html.
The XML report (machine-parseable) is at the same path with .xml extension.
Read the XML or HTML to extract per-class coverage. Key classes to check:
StrokeBuffer — pure data structure, should be near 100%SessionAdapter (statusIcon, formatSessionTime) — pure utility functionsPenOverlay (rawDrawingAction) — pure decision functionMainActivity — Android-coupled, low coverage expected (needs instrumentation tests)Present findings as:
Coverage Summary
| Component | File | Line Coverage | Key Gaps |
|---|---|---|---|
| server | app.rs | 97% | - |
| server | config.rs | 78% | load() error paths |
| android | StrokeBuffer | 95% | - |
| android | MainActivity | 0% | Android-coupled, needs instrumentation |
Uncovered Areas Needing Tests
For each gap, explain:
main.rs and mock_device.rs are binary entrypoints — low coverage is expected and not worth flagging.MainActivity.kt requires Android instrumentation tests (not JUnit) — flag this as a known gap but don't suggest unit tests for Android framework code.