원클릭으로 Manus에서 모든 스킬 실행

review-tool-volume-management

스타30

포크1

업데이트2026년 6월 27일 09:20

Manage rawsql-ts external review-tool usage for CodeRabbit or similar AI review bots when PRs are stacked, small, generated, broad, rate-limited, or likely to consume review quota before the branch is ready.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

mk3008

mk3008/rawsql-ts

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Review Tool Volume Management

Use this skill before requesting external AI review, when CodeRabbit reports rate limits, or when a branch is being updated repeatedly before it is ready for human review.

Workflow

Decide whether the PR is ready for external review:
- implementation complete,
- focused verification run,
- PR readiness body validated,
- self-review blockers resolved or surfaced.
If the PR is still changing quickly, avoid manual review triggers until the next ready checkpoint.
For stacked or closely related small PRs, request review on the PR where the source decision is clearest, then use the review result to update the rest.
For generated or broad diffs, use broad-generated-diff-review-packet before requesting bot review.
When a rate-limit comment appears, record it as review coverage unavailable, not as a code finding.
If review is still needed after the refill window, trigger one review after the branch and PR body are stable.
Do not treat COMMENTED bot review states as approval.

PR Notes

Mention review-tool limits only when they affect review confidence. Keep the note short:

External AI review was rate-limited; repository checks and self-review are the current evidence.
External AI review requested after readiness validation.

Constraints

Do not spend review quota on WIP pushes when local checks or PR readiness are still failing.
Do not hide skipped or rate-limited review coverage if the final claim depends on it.
Do not copy bot marketing, tips, or generated poems into repository evidence.

이 저장소의 다른 Skills

같은 저장소

rawsql-task-orchestrator

mk3008/rawsql-ts

Assess and dispatch rawsql-ts developer tasks by tracing repository impact, concept and package boundaries, verification cost, difficulty, risk, model and reasoning effort, and Codex worktree requirements. Use when a new rawsql-ts issue, bug, feature, refactor, investigation, CI failure, review request, migration, or documentation change must be analyzed before action or handed to a new Codex task.

2026-07-1230

developer-attainment-reporting

mk3008/rawsql-ts

Report per-item attainment for completed rawsql-ts developer work.

2026-07-1030

package-spec-review

mk3008/rawsql-ts

Review tracked rawsql-ts package-level Scope, Test Policy, Authority Model, Technology Policy, review-plan, and generated review views before package implementation or documentation changes. Use only when those package-owned artifacts exist in the checked-out base.

2026-07-1030

developer-pr-readiness

mk3008/rawsql-ts

Prepare rawsql-ts pull requests with the repository PR template and local readiness gate so required merge, CLI migration, and scaffold proof sections are not missed.

2026-07-1030

developer-pre-pr-retro-gate

mk3008/rawsql-ts

Check tmp/RETRO.md before PR or human review so unresolved retro items do not slip through rawsql-ts developer workflow.

2026-07-1030

developer-retro-capture

mk3008/rawsql-ts

Capture meaningful recognition mismatches, false completion claims, and verification misses into tmp/RETRO.md for rawsql-ts developer work.

2026-07-1030

name	review-tool-volume-management
description	Manage rawsql-ts external review-tool usage for CodeRabbit or similar AI review bots when PRs are stacked, small, generated, broad, rate-limited, or likely to consume review quota before the branch is ready.

Review Tool Volume Management

Use this skill before requesting external AI review, when CodeRabbit reports rate limits, or when a branch is being updated repeatedly before it is ready for human review.

Workflow

Decide whether the PR is ready for external review:
- implementation complete,
- focused verification run,
- PR readiness body validated,
- self-review blockers resolved or surfaced.
If the PR is still changing quickly, avoid manual review triggers until the next ready checkpoint.
For stacked or closely related small PRs, request review on the PR where the source decision is clearest, then use the review result to update the rest.
For generated or broad diffs, use broad-generated-diff-review-packet before requesting bot review.
When a rate-limit comment appears, record it as review coverage unavailable, not as a code finding.
If review is still needed after the refill window, trigger one review after the branch and PR body are stable.
Do not treat COMMENTED bot review states as approval.

PR Notes

Mention review-tool limits only when they affect review confidence. Keep the note short:

External AI review was rate-limited; repository checks and self-review are the current evidence.
External AI review requested after readiness validation.

Constraints

Do not spend review quota on WIP pushes when local checks or PR readiness are still failing.
Do not hide skipped or rate-limited review coverage if the final claim depends on it.
Do not copy bot marketing, tips, or generated poems into repository evidence.