ai-generated-business-code-review_skill

This skill evaluates AI-generated business code quality, scores 0-10, assesses risk, and generates must-fix items with concrete evidence.
  • Python

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openharmonyinsight/openharmony-skills --skill ai-generated-business-code-review

  • SKILL.md3.6 KB

Overview

This skill evaluates AI-generated business and application code for correctness, robustness, maintainability, performance, and security. It produces a numeric 0–10 score, a concise risk level, and a must-fix checklist with concrete evidence. For C++ code, it enforces OpenHarmony C++ and OpenHarmony security review constraints as mandatory checks.

How this skill works

I identify the language and whether the code is business logic or test code, and refuse test-code reviews in favor of a unit-test review workflow. I inspect behavior against requirements, edge cases, error handling, resource management, and security controls. For C++ code I apply openharmony-cpp and openharmony-security-review as hard constraints and flag any violations in evidence and must-fix items.

When to use it

  • Review AI-generated backend, service, or application code for production readiness
  • Need a numeric quality score plus a clear risk level and prioritized fixes
  • Require explicit evidence lines or snippets to support findings
  • Assess C++ business code for OpenHarmony coding and security compliance
  • Validate security, resource management, and error-handling before deployment

Best practices

  • Provide the codebase or specific files and relevant requirements or usage scenarios
  • Include expected inputs, error modes, and performance constraints for accurate scoring
  • Mark C++ reviews as such so OpenHarmony constraints are applied
  • Expect at least two concrete evidence items; lack of evidence lowers score
  • Request follow-up iterations after fixes to verify remediations

Example use cases

  • Score a new AI-generated microservice implementation and get a must-fix checklist
  • Audit C++ service code to ensure OpenHarmony C++ and security rules are met
  • Compare two AI-generated implementations by normalized 0–10 rubric
  • Identify missed edge cases, swallowed exceptions, and resource leaks before release
  • Produce developer-facing fixes with file/line or snippet references

FAQ

A sum of five dimensions (Correctness, Robustness, Maintainability, Performance, Security) each scored 0–2, totaling 0–10.

How are C++ OpenHarmony issues reported?

Any OpenHarmony C++ or OpenHarmony security violation is called out explicitly in Must-fix and Key Evidence and may raise the risk to Blocker.

What counts as sufficient evidence?

At least two citations of functions, classes, file paths, line ranges, or code snippets showing the issue; otherwise the score is reduced.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational