Agent skill · Security

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.

TencentCloudBasegithub.com/TencentCloudBaseGitHub ↗
claude-codecursorMIT
Install
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloudbase-code-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 11
SKILL.md size: 4 KB
Bundled scripts: none
Version: 2.25.10
Path: config/.claude/skills/cloudbase-code-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,066
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Sibling skills (local only) 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. # CloudBase Code Review > **One-liner**: After implementing CloudBase features, call this skill to catch common mistakes before the grader does. ## When to use Call this skill **after** completing a CloudBase implementation task, before declaring done: - You implemented auth (login / register / route guard) - You created database tables or wrote CRUD (NoSQL / PostgreSQL / MySQL) - You set up CloudBase Storage (file upload, hosting) - You configured security rules or RLS policies - You wrote MCP-dependent code ## How it works 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 loc

What's inside
Steps it walks through
  1. Sibling skills (local only)
  2. When to use
  3. How it works
  4. Rule index
  5. Rule boundary
  6. Quick start
  7. Rule format
  8. Reference index
Ships with 10 files
  • references/RULES_INDEX.md
  • references/lint-rules/README.md
  • references/rules/cross-cutting/AUTH001.md
  • references/rules/cross-cutting/SKILL001.md
  • references/rules/postgresql/PG-CR001.md
  • references/rules/postgresql/PG-CR002.md
  • references/rules/postgresql/PG-CR003.md
  • references/rules/postgresql/PG-CR004.md
  • references/rules/postgresql/PG-CR005.md
  • references/rules/storage/STORAGE001.md
Commands it runs
Step 1: Read relevant rules for identified modules
references/rules/cross-cutting/AUTH001.md
references/rules/postgresql/PG-CR001.md
then run: node cloudbase-lint.mjs --project-dir .
Step 2: For each applicable rule, read the "LLM 检查" section
and manually inspect your code before claiming done.
More from CloudBase-AI-Toolkit
All skills →
About this skill
What does the cloudbase-code-review skill do?

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.

How do I install it?

Run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloudbase-code-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From TencentCloudBase/CloudBase-AI-Toolkit, a repository with 1,066 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going