SuperAPI AI Directory

code-review

Coding & development

View repository

Updated 11-05 16:54

About this skill

Code Review
  1. Ensure every code change has test cases that verify the behavior the code should have and the behavior it should prevent.
  2. Ensure bug-fix pull requests include regression tests proving the bug was reproducible before the change and is fixed after it; if the reviewer cannot run the comparison, use the available evidence and state this limitation.
  3. Ensure terminology changes use terminology consistent with the repository; community-authored catalog content and documentation generated from it are outside the scope of this check.
  4. Identify the affected domain and read design/ before evaluating architectural consistency. CLI command changes use design/cli.md; agent integration uses design/integration.md; workflow step types use design/workflow-step.md. Read other design documents as relevant; there is no need to read all documents for every PR.
  5. Check changes against applicable design requirements, including implementation boundaries, ownership, lifecycle, and delivery requirements. Cite documents rather than repeating their rules in this skill. Every reported inconsistency must cite the document and section.
  6. Distinguish unexplained design violations from intentional design changes. Evaluate the rationale and evidence for intentional changes; updating the design document alone is not sufficient to justify the implementation.