ascendc-code-review

Invoke the skill with a file review request and it routes to the file-review workflow, which identifies the code side (Kernel, Tiling, or Host), extracts applicable clauses from the reference rule libraries, and checks each rule with evidence collection. Findings are reported with severity levels.

It checks API best practices (DataCopy 32-byte alignment, AllocTensor/FreeTensor pairing, CrossCoreSetFlag symmetry), performance rules (double buffering, UB/L1 capacity, tail-block handling), red-line issues (division by zero, integer overflow, int64 GM offsets), and TOPK高频 problems like unchecked return values.

Yes, PR review is a dedicated workflow triggered by PR references. It supports repositories such as ops-transformer, ops-math, ops-nn, and ops-cv, infers the repo from the PR URL, and automatically switches strategy for large PRs.

It uses a bundled static analysis script that performs interval propagation on arithmetic expressions. You provide the expression and variable ranges, and it reports overflow, wraparound, or division-by-zero risks with boundary counter-examples and sensitivity analysis.

Yes, the SUNSET clauses check for deprecated aclrt, aclnn, and acl.op APIs plus deprecated header paths and libraries. A script dynamically parses official deprecation documentation to generate the current sunset symbol list.

The bounds-checking script only analyzes arithmetic expressions for overflow, wraparound, and division by zero; it does not cover type conversion truncation or signed/unsigned comparison semantics. Rule checks also require consulting the latest Ascend C API documentation when clauses may be outdated.