rdkcentral

Run and interact with the BartonCore reference application. Use when the user wants to start the reference app, commission devices, execute/read/write resources, or troubleshoot runtime issues. Covers CLI flags, interactive commands, isolated session management, and known pitfalls.

Format C/C++ code in BartonCore. Use when the user wants to format source files, understand formatting conventions, or fix formatting issues. Covers clang-format usage, the diff-only rule, manual blank-line conventions that clang-format cannot enforce, and the pre-commit hook.

Validate SBMD (Spec-Based Matter Driver) v4 specification files. Use when the user has edited .sbmd.js files, wants to check schema conformance, or verify driver structure. Covers the validation script, JSON schema, spec file locations, and automatic build-time validation.

Build BartonCore from source. Use when the user wants to compile the project, rebuild after code changes, reconfigure CMake options, or understand the build system. Covers the build.sh convenience script, incremental cmake builds, CMake configuration flags, and the development build profile.

Debug BartonCore applications and tests. Use when the user needs to set breakpoints, step through code, inspect state, or diagnose crashes. Covers three workflows — gdb for the C/C++ reference app and unit tests, pdb/debugpy for Python integration tests, and gdb-with-Python for debugging C code called from Python tests.

Work with Matter test devices in BartonCore. Use when the user wants to start Matter sample apps, use chip-tool to commission or control devices, work with matter.js virtual devices for integration testing, or create new custom virtual device types. Covers pre-built sample apps, chip-tool commands, and the matter.js sideband API.

Run BartonCore Python integration tests. Use when the user wants to run integration tests, verify end-to-end behavior, run specific test files, or filter tests by keyword or marker. Covers pytest via the py_test.sh wrapper, ASAN preloading, test filtering, prerequisites, and the CI all-in-one script.

Run BartonCore C/C++ unit tests. Use when the user wants to run unit tests, verify code changes pass tests, run a specific test, or list available tests. Covers ctest commands, test filtering, CMocka (C) and Google Test (C++) frameworks, and test source locations.

Disciplined diagnosis loop for meminsight parser bugs, runtime failures, and regressions using deterministic fixture-first feedback.

Structured requirement interview for larger changes, grounded in OpenSpec capabilities and repository constraints.

Use for implementation tasks to enforce OpenSpec-first behavior, As-Is alignment, and change-spec gating for behavior changes.

Vertical-slice test-driven workflow for meminsight features and fixes, anchored to OpenSpec capabilities and fixture validation.

Break plans into implementation issues linked directly to OpenSpec capability IDs and acceptance checks.

Provide a system-level map of meminsight modules, call flow, and capability ownership for onboarding and design clarity.

Use when implementing or reviewing pagetypeinfo/buddyinfo collection with format drift tolerance, fallback behavior, and low-overhead parsing.

Use when changing CSV/JSON report fields to preserve backward compatibility and document schema-impacting changes clearly.

Generate BDD (Behavior Driven Development) feature files from remote debugger source code analysis. Use for creating Gherkin-format documentation of RBUS event handling, static/dynamic profile processing, command execution, harmful command detection, log archive and upload, deep sleep handling, and uploadRRDLogs C API orchestration. Produces gap analysis between feature files and L2 test implementations.

Analyze C/C++ code for memory safety issues including leaks, use-after-free, buffer overflows, and provide fixes. Use when reviewing memory management, debugging crashes, or improving code safety.

Verify C/C++ code is platform-independent and portable across embedded platforms. Use when reviewing code for cross-platform deployment or preparing for new hardware targets.

Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) in the standard test container. Use when validating code changes or debugging before committing.

Create and maintain comprehensive technical documentation for embedded systems projects. Use for architecture docs, API references, developer guides, and system documentation following best practices.

Analyze C/C++ code for thread safety issues including race conditions, deadlocks, and improper synchronization. Use when reviewing concurrent code or debugging threading issues.

Triage remote debugger behavioral issues on RDK devices by correlating device log bundles with the remote debugger source tree. Covers daemon startup failures, profile processing issues, uploadRRDLogs failures, RBUS communication problems, configuration errors, and archive or cleanup failures. The user states the issue; this skill guides systematic root-cause analysis regardless of issue type.

Analyze code-to-spec coverage in an Openspec project and generate a compliance score and report.

Update existing Openspec spec files to match the standard spec template format. Ensures consistency and completeness across all specs in a project.

Add Mermaid diagrams to a Slidev presentation slide.

Add new slides with various layouts to a Slidev presentation.

Build a static SPA or export a Slidev presentation to PDF.

Initialize a new Slidev project with slides.md and configuration.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Analyze C++17 MemCapture code for memory safety issues including resource leaks, use-after-free, unclosed ifstream files, dangling iterators, and improper shared_ptr cycles. Use when reviewing metric code, file parsers, or report generation.

Verify MemCapture C++17 code is correct and portable across all supported RDK device platforms (AMLOGIC, AMLOGIC_950D4, REALTEK, REALTEK64, BROADCOM, MEDIATEK). Use when reviewing platform-specific metric code, adding a new platform target, or auditing sysfs/proc path assumptions.

Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) on the MemCapture codebase. Use when validating code changes or debugging before committing.

Analyze MemCapture C++17 code for thread safety issues including race conditions on shared metrics maps, deadlocks in metric shutdown, improper std::atomic usage for mQuit flags, and collection thread lifecycle problems. Use when reviewing concurrent metric code or debugging threading issues.

Triage MemCapture behavioural issues by correlating the HTML/JSON report output and stderr logs with the MemCapture source tree. Covers metric collection failures, missing data in reports, platform-specific sysfs/proc read errors, process grouping problems, and report generation issues. The user states the issue; this skill guides systematic root-cause analysis.

Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification, L1 unit tests, L2 integration tests) in the standard test container. Use when validating code changes or debugging before committing.

Analyze GitHub PR changes for embedded C/C++ code and generate comprehensive REVIEW.md with visual diffs, impact assessment, and regression risk analysis. Use when: reviewing pull requests, analyzing code changes, identifying functional regressions, assessing memory/thread safety impact, validating embedded systems changes.

Triage any Telemetry 2.0 behavioral issue on RDK devices by correlating device log bundles with source code. Covers hangs, under-reporting, over-reporting, duplicate reports, CPU/memory spikes, scheduler anomalies, rbus problems, and test gap analysis. The user states the issue; this skill guides systematic root-cause analysis regardless of issue type.

Verify C/C++ code is platform-independent and portable across embedded platforms. Use when reviewing code for cross-platform deployment or preparing for new hardware targets.

Create and maintain comprehensive technical documentation for embedded systems projects. Use for architecture docs, API references, developer guides, and system documentation following best practices.

Generate BDD (Behavior Driven Development) feature files from RFC Manager source code analysis. Use for creating Gherkin-format documentation of XConf communication, TR-181 parameter processing, mTLS certificate selection, AccountID handling, Maintenance Manager integration, and reboot trigger behavior. Produces gap analysis between feature files and L2 test implementations.

Verify C/C++ code is platform-independent and portable across embedded platforms. Use when reviewing code for cross-platform deployment or preparing for new hardware targets.

Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) in the standard test container. Use when validating code changes or debugging before committing.

Triage RFC (Remote Feature Control) module behavioral issues on RDK devices by correlating device log bundles with the RFC module source tree. Covers rfcMgr daemon startup failures, XConf communication issues, TR181 parameter processing errors, IARM bus problems, mTLS certificate failures, and reboot trigger failures. The user states the issue; this skill guides systematic root-cause analysis regardless of issue type.

Generate BDD (Behavior Driven Development) feature files from tr69hostif source code analysis. Use for creating Gherkin-format documentation of TR-181 parameter handlers, daemon lifecycle, WebPA/Parodus communication, HTTP server protocol, and RFC store behavior. Produces gap analysis between feature files and L2 test implementations.

Triage any tr69hostif behavioral issue on RDK devices by correlating device log bundles with source code. Covers daemon hangs, TR-069/CWMP RPC failures, TR-181 parameter get/set errors, WebPA/parodus handler faults, RFC parameter override issues, CPU/memory spikes, and test gap analysis. The user states the issue; this skill guides systematic root-cause analysis regardless of issue type.

Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) in the standard test container. Use when validating code changes or debugging before committing.

Analyze code-to-spec coverage in an Openspec project and generate a compliance score and report.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Update existing Openspec spec files to match the standard spec template format. Ensures consistency and completeness across all specs in a project.

Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) in the standard test container. Use when validating code changes or debugging before committing.

Triage any dcm-agent behavioral issue on RDK devices by correlating device log bundles with source code. Covers daemon hangs, log upload failures, DCM configuration errors, uploadSTBLogs failures, backup_logs issues, USB log upload problems, RBUS communication errors, and cron scheduling issues. The user states the issue; this skill guides systematic root-cause analysis regardless of issue type.

Diagnose issues from logs, traces, or runtime symptoms with OpenSpec and repository docs as source of truth. Use when debugging defects, validating incident hypotheses, or preparing a fix plan.

Deep educational walkthrough of code and architecture for developers at any level, using relatable analogies and step-by-step progression from fundamentals to advanced behavior.

Use this to fix discovered static analysis / Coverity issues over selected components in the entservices repo. Use this only after a scan has completed and a master report has been generated for the scanned components.

Use this to run static analysis over components in the entservices repo and generate a master report. Use this when you are asked to run a Coverity Scan and produce the CSV report for the scanned components.