跳到正文
cccskills
免费在 GitHub 公开

review-automation-orchestrator

Use when running or scheduling periodic repository review cycles that must dispatch the correct reviewer, aggregate findings, and escalate outcomes into reports, issues, or corrective PRs across API contracts, documentation freshness, code quality, and CloudBase skill quality.

中文简介正在准备中。当前显示原文说明。

TencentCloudBase/CloudBase-AI-Toolkit
查看安装方法

包含的文件（2）

  • SKILL.md4.5 KB
  • references/escalation-matrix.md1.2 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Review Automation Orchestrator

Coordinate recurring repository review work without turning one skill into every reviewer at once.

When to use this skill

Use this skill when you need to:

  • Run a periodic repository review across several quality dimensions
  • Decide which specialized review skill should own each finding type
  • Aggregate review results into one report with clear escalation
  • Convert high-confidence, low-risk findings into corrective PRs when feasible
  • Configure or run a scheduled review cycle without duplicating the underlying reviewer logic

Do NOT use for:

  • Acting as the primary reviewer for API contracts, docs, or code quality by itself
  • Replacing the existing CloudBase skill review flow under skill-authoring
  • Fixing a single known issue without a broader review cycle
  • Merging PRs or making final release decisions

Workflow

Phase 1 — Define the run

  1. Clarify whether the run is one-time or periodic.
  2. Define the review surfaces and target outputs:
    • report only
    • issue + report
    • fix + PR
  3. Read references/escalation-matrix.md before dispatching work.

Phase 2 — Dispatch to the right reviewer

Route by finding type, not by convenience:

  • CloudBase API contract correctness → api-contract-review
  • Published docs and README drift → doc-freshness-review
  • Broad code hygiene and proactive repository health → codebase-audit
  • Existing open PR triage and repair → pr-review-fix
  • CloudBase source skill quality under config/source/skills → skill-authoring, then load references/repo-skill-review.md and references/cloudbase-skill-review.md

Do not create a redundant top-level CloudBase skill reviewer when the existing skill-authoring flow already covers it.

Phase 3 — Normalize findings

  1. Deduplicate overlaps between reviewers.
  2. Normalize each finding with:
    • scope
    • severity
    • confidence
    • smallest useful fix batch
    • recommended action from the escalation matrix
  3. Keep reports readable: separate API, docs, code, and skill findings.

Phase 4 — Escalate

  1. Use report only for lower-confidence or lower-impact findings.
  2. Use issue + report for confirmed but broader or riskier problems.
  3. Use fix + PR when the finding is confirmed, mechanically fixable, and small enough for a focused review.
  4. Prefer concrete PRs over issue-only churn when the path is already clear and low-risk.

Phase 5 — Scheduling discipline

  1. If the user asks for recurrence, create automation that runs the review cycle and stores the task prompt separately from schedule details.
  2. Keep the scheduled prompt short and routing-focused.
  3. Do not duplicate reviewer checklists inside the automation definition.

Routing

TaskRead
Decide escalation from severity and confidencereferences/escalation-matrix.md
Review CloudBase API contract correctnessapi-contract-review
Review doc and README driftdoc-freshness-review
Run broad repository code reviewcodebase-audit
Repair existing PRs after reviewpr-review-fix
Review CloudBase source skillsskill-authoring

Evaluation prompts

Should-trigger

  1. Run a weekly repository review that checks CloudBase API contracts, docs freshness, and skill quality, then decide what should become PRs.
  2. Help me set up a periodic review flow that routes findings to the right reviewer and escalates only the high-confidence fixes.
  3. Aggregate findings from code, docs, and CloudBase skill review into one actionable maintenance report.

Should-not-trigger

  1. Review this one MCP tool for parameter casing errors.
  2. Audit doc/ for stale links and missing files.
  3. Rewrite a CloudBase source skill description to improve its trigger wording.

Minimum self-check

  • Did I dispatch each finding class to the correct specialized reviewer?
  • Did I reuse skill-authoring for CloudBase skill review instead of inventing a duplicate flow?
  • Did I normalize findings by severity, confidence, and smallest useful fix batch?
  • Did I choose report, issue, or PR based on evidence rather than habit?
  • If the run is periodic, did I keep the automation prompt focused on routing instead of embedding whole checklists?

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

ai-model-nodejs

免费

Use this skill for Node.js backend AI via @cloudbase/node-sdk (>=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration. The only SDK supporting image generation (ai.createImageModel + generateImage). Text via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*; model ids (e.g. deepseek-v4-flash, glm-5, kimi-k2.6) go in the `model` field of generateText/streamText. MUST run two-step preflight before code — see body. NOT for browser/Web (use ai-model-web) or Mini Program (use ai-model-wechat).

中文简介正在准备中。当前显示原文说明。

TencentCloudBase/CloudBase-AI-Toolkit11412026年10月19日 更新

ai-model-web

免费

Use this skill when a browser/Web app (React, Vue, Next, Nuxt, static sites, SPAs, dashboards, AI chat UI, 页面, 前端, 网页) needs AI models via @cloudbase/js-sdk. Default routing for Web/frontend AI — call directly from the browser, do NOT propose a Node.js proxy. Covers generateText and streamText; models via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*, model id in the `model` field. MUST run two-step preflight before code — see body. NOT for Node.js backend (use ai-model-nodejs), Mini Program (use ai-model-wechat), or image generation (Node SDK only).

中文简介正在准备中。当前显示原文说明。

TencentCloudBase/CloudBase-AI-Toolkit11412026年10月19日 更新

ai-model-wechat

免费

Use this skill for WeChat Mini Program AI via wx.cloud.extend.AI (小程序, wx.cloud apps). Covers generateText and streamText with callbacks (onText, onEvent, onFinish); streamText needs a data wrapper, generateText returns the raw response. Models via wx.cloud.extend.AI.createModel with groups hunyuan-exp (小程序成长计划), cloudbase (main managed), or custom-*; model id goes in the data wrapper `model` field. MUST run two-step preflight before code — see body. NOT for browser/Web (use ai-model-web), Node.js backend (use ai-model-nodejs), or image generation (use ai-model-nodejs).

中文简介正在准备中。当前显示原文说明。

TencentCloudBase/CloudBase-AI-Toolkit11412026年10月19日 更新

api-contract-review

免费

Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.

中文简介正在准备中。当前显示原文说明。

TencentCloudBase/CloudBase-AI-Toolkit11412026年10月19日 更新

auth-nodejs-cloudbase

免费

CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets. This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system into CloudBase; not when configuring providers or building client login UI.

中文简介正在准备中。当前显示原文说明。

TencentCloudBase/CloudBase-AI-Toolkit11412026年10月19日 更新

auth-tool-cloudbase

免费

CloudBase auth provider configuration and login-readiness guide. This skill should be used when users need to inspect, enable, disable, or configure auth providers, publishable-key prerequisites, login methods, SMS/email sender setup, or other provider-side readiness before implementing a client or backend auth flow.

中文简介正在准备中。当前显示原文说明。

TencentCloudBase/CloudBase-AI-Toolkit11412026年10月19日 更新

查看 TencentCloudBase 的全部技能

报告此技能的问题