跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

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.

数据库与数据1.1kskills/review-automation-orchestrator/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性，你确认后才安装。

读取 https://funcoding.ai/skills/tencentcloudbase/cloudbase-ai-toolkit/review-automation-orchestrator/install.md ，按里面的步骤帮我安装这个 Skill。

SKILL.md

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?

相似的 Skill

xlsx
anthropics/skills180k

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

数据库与数据

deprecation-and-migration
addyosmani/agent-skills103k

deprecation-and-migration

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.

数据库与数据

host-observer
thedotmack/claude-mem98k

host-observer

Use this when fulfilling claude-mem observer jobs on Grok Bot: reply only skip_summary or one full observation XML, never prose.

数据库与数据

babysit
thedotmack/claude-mem98k

babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

数据库与数据

mem-search
thedotmack/claude-mem98k

mem-search

Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

数据库与数据

Agent Cost Report
thedotmack/claude-mem98k

Agent Cost Report

Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.

数据库与数据