wandelbotsgmbh/wandelbots-nova / nova/agent_skills/nova-app-review
nova-app-review
VerifiedReview a robot cell application built on the Wandelbots NOVA Python SDK (wandelbots-nova) for safety, motion, PLC/IO, async runtime, performance, lifecycle, device handling and NOVA SDK usage, and report findings with severity, evidence and concrete fixes. Use when the user asks to review, audit, check, lint or harden a NOVA app, a @nova.program, a NOVAx app or any robot application; asks about best practices, common pitfalls, cycle time, safety or commissioning readiness; or asks 'is my robot code OK?'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.5 KB |
| references/nova-sdk-mapping.md | markdown | 9.3 KB |
| references/reference-numbers.md | markdown | 1007 B |
| references/rules/async.md | markdown | 4.2 KB |
| references/rules/configuration.md | markdown | 1.5 KB |
| references/rules/devices.md | markdown | 3.0 KB |
| references/rules/errors.md | markdown | 2.5 KB |
| references/rules/io.md | markdown | 3.5 KB |
| references/rules/lifecycle.md | markdown | 3.2 KB |
| references/rules/motion.md | markdown | 6.8 KB |
| references/rules/observability.md | markdown | 1.6 KB |
| references/rules/performance.md | markdown | 4.8 KB |
| references/rules/safety.md | markdown | 9.6 KB |
| references/rules/structure.md | markdown | 1.3 KB |
| references/rules/testing.md | markdown | 1.0 KB |
| scripts/scan.py | script | 38.4 KB |
references/rules/devices.md
View on GitHub# Devices (DEV)
## DEV-001 · Verify gripper state by sensor after every actuation
`severity: error` · `scope: robotics` · `detect: static+review`
**Rule.** After open/close, wait (with timeout) for the sensor feedback of the expected state.
"Command sent" is not "part gripped". Lift the part only after grip confirmation.
---
## DEV-002 · Validate vision results before using them as targets
`severity: error` · `scope: robotics` · `detect: review`
**Rule.** A camera result becomes a motion target only after these checks: result present, match
score above threshold, pose within the expected workspace/ROI bounds, orientation within limits,
transformed into the correct frame (camera→robot calibration applied once, centrally).
**Detect.** Camera/vision return value used directly in a motion action; only a `None` check.
---
## DEV-003 · Force-controlled motion has limits, abort and timeout
`severity: error` · `scope: robotics` · `detect: static+review`
**Rule.** Every force-guided/contact motion defines a force threshold, a maximum travel distance, a
timeout, and the action taken on abort (stop, retract). Direction mappings are explicit constants.
NOVA: an IO-driven stop condition can be passed as `execute(..., pause_on_io=...)`. Check that it
is not dropped in simulation (SAF-011).
---
## DEV-004 · Network devices use async clients with timeouts
`severity: error` · `scope: robotics` · `detect: static`
**Rule.** HTTP/TCP device clients (grippers, cameras, IO-Link masters) are async, created once,
configured with explicit connect/read timeouts, and retried on connect.
**Detect.** `requests.` / `urllib.request` / blocking `socket` in device code; `httpx.AsyncClient()`
created per call or without `timeout=`.
---
## DEV-005 · Track tool contents and check before pick/place
`severity: warning` · `scope: robotics` · `detect: review`
**Rule.** Maintain a register of what each gripper holds. Before a pick, assert that it is empty;
before a place, assert that it holds the expected part. Update the register only after sensor
confirmation (DEV-001).
---
## DEV-006 · Validate device parameter invariants before writing
`severity: warning` · `scope: robotics` · `detect: review`
**Rule.** Check documented device constraints in code before writing parameters (e.g. gripper
positions `base < shift < work`, force/speed ranges). Raise with a clear message rather than letting
the device fault with a numeric error code.
---
## DEV-007 · Re-establish device readiness after mode change or fault
`severity: warning` · `scope: robotics` · `detect: review`
**Rule.** After device mode changes, power cycles or faults, re-check and restore readiness (motor
on, referenced/homed, error cleared) before the next command. Grippers may lose their reference
after a fault.
---
## DEV-008 · Open gripper before approach
`severity: warning` · `scope: robotics` · `detect: review`
**Rule.** Ensure the gripper is open (and confirmed) before the final approach to a part. Do this in
parallel with the free-space move to save cycle time (PERF-008).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |