Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tencentcloudbase/cloudbase-code-review
Code review and validation for CloudBase projects. After writing code for Web / miniprogram / CloudRun / cloud-function projects, call this skill to check for known pitfalls — auth guard misuse, missing database tables, RLS misconfiguration, storage domain setup, and SDK API misuse. Supports automated lint scripts (regex-based) + LLM semantic review.
Passed 20 of 22 test cases with the skill, and 9 of 22 without it.
and 13 more in the full report
12 fixed8 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our PostgreSQL database integration involves multi-table joins, custom indexing, and complex trigger functions on CloudBase. What range of rule files covers PostgreSQL code reviews in the reference directory?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the rule range from PG-CR001.md through PG-CR005.md in references/rules/postgresql/. | Missed | Passed |
The instructions your model reads when the skill loads.
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.
If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.
One-liner: After implementing CloudBase features, call this skill to catch common mistakes before the grader does.
Call this skill after completing a CloudBase implementation task, before declaring done:
The skill runs in two layers:
| Layer | Method | Speed | What it catches |
|---|---|---|---|
| Lint (optional) | No executable script is shipped. If the user approves running lint, review the code block in references/lint-rules/README.md, copy it to a temporary local cloudbase-lint.mjs, then run node cloudbase-lint.mjs --project-dir <path> | Seconds | Deterministic regex checks — wrong API calls, missing configs, pattern mismatches |
| LLM review | Read each rule's "LLM 检查" section, inspect code semantically | Variable | Semantic issues — route guard logic, RLS completeness, architecture-level problems |
See references/RULES_INDEX.md for the full matrix (module × frontend type → applicable rules).
Do not promote a single failed run or case-specific workaround into a hard rule. A rule should be backed by stable SDK/API documentation, repeated failures, or deterministic runtime behavior. Case-specific observations belong in attribution reports; only broadly applicable constraints should enter RULES_INDEX.md or the optional lint checklist.
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.