chsh-sk-ncs-4-test-verification

Runs code review, build verification, host tests, and documentation audits for NCS firmware projects.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-4-test-verification-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-ncs-4-test-verification
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-ncs-4-test-verification
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-4-test-verification-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before releasing or demoing an NCS (nRF Connect SDK) firmware project, teams need a structured, hardware-free verification pass covering code quality, build integrity, and documentation consistency. This Skill automates that verification phase and produces a standardized report with clear routing for any issues found. ## Core Features & Use Cases - Independent Code Review: Delegates review to a separate code-reviewer agent so the implementation is checked by a fresh perspective, with P0/P1/P2 severity findings. - Build & Format Verification: Runs the exact build commands documented in the project README, enforces zero compiler warnings, and checks clang-format compliance using the NCS toolchain. - Host Tests & PRD Traceability: Executes native_sim/ztest suites when present, reads code FR-by-FR against PRD acceptance criteria, and audits the PRD → Specs → Code → README version chain. - Use Case: After merging a feature branch to main in an nRF70 Wi-Fi firmware project, run this Skill to produce a timestamped verification report in docs/qa-test/ confirming the build is clean, requirements are satisfied, and docs are consistent before hardware validation. ## Quick Start Ask Claude to run the NCS verification skill on the current project to perform code review, build checks, host tests, and a documentation audit, then generate the verification report.

Frequently Asked Questions about chsh-sk-ncs-4-test-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an NCS firmware project without hardware?

Run this verification skill, which performs code review, clang-format checks, README-based build verification, native_sim/ztest host tests, and a PRD satisfaction check entirely on the host. It produces a timestamped report under docs/qa-test/ with pass/fail verdicts and routing.

How to run Zephyr ztest suites on native_sim with twister?

Use west twister -p native_sim -T tests/ --inline-logs to execute all host test suites. Note that twister exits nonzero if any suite fails, so read the printed summary table rather than relying on the exit code alone.

Does this verification require physical nRF hardware?

No, the entire verification runs on the host and can execute in CI. Checks that cannot be confirmed without hardware are marked as not visible and handed off as priority test cases to the hardware validation phase.

Why does clang-format report different violations than expected?

Version mismatches between system clang-format and the NCS toolchain binary cause inconsistent results. Always use the NCS toolchain launcher (nrfutil sdk-manager toolchain launch -- clang-format) rather than the system binary.

What happens when verification finds a P0 issue?

Any P0 finding, including security issues, failing host tests, build failures, or PRD criterion mismatches, stops verification and routes immediately back to the implementation phase for fixes. Only clean results proceed to hardware validation.