beesdk-review-and-close

Reviews BeeSDK changes against approved Issues and returns a consolidated verdict with PR close package.

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/beesyst/beesdk --skill beesdk-review-and-close-beesyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beesdk-review-and-close
Source: https://github.com/beesyst/beesdk/tree/main/.agents/skills/beesdk-review-and-close
Command: npx skills add https://github.com/beesyst/beesdk --skill beesdk-review-and-close-beesyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Final code review of BeeSDK changes is often inconsistent: reviewers may inspect the wrong worktree, read partial diffs, or miss blocking findings like unrelated refactoring or contract violations. This Skill enforces a rigorous, read-only review workflow that verifies the exact target worktree, consumes the complete manifest and diff, evaluates every acceptance criterion, and returns one consolidated verdict. ## Core Features & Use Cases - Exact target verification: Resolves the precise worktree, branch, and base branch through MCP tools before reviewing, refusing to issue a verdict on mismatched targets. - Complete evidence consumption: Paginates through the full review manifest and diff, requiring a consistent snapshot and rejecting truncated or partial data. - Structured verdicts: Returns either an approval with a PR body and squash commit recommendation, or a detailed blocker list with exact before/after corrections plus a ready-to-use correction prompt for Copilot or Codex. - Use Case: After a developer finishes a BeeSDK feature branch, supply the approved Issue, worktree path, and implementation evidence; the Skill performs a read-only review and returns either an approval package or a consolidated list of blocking fixes. ## Quick Start Review the completed BeeSDK implementation in the specified worktree against the approved Issue and return the final verdict with a PR close package.

Frequently Asked Questions about beesdk-review-and-close

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a final code review on a BeeSDK feature branch?

Supply the approved Issue, exact worktree path, expected branch and base branch, and implementation evidence. The Skill verifies the target through MCP tools, reads the complete manifest and diff, evaluates every acceptance criterion, and returns a single verdict.

What inputs are required for a BeeSDK review and close workflow?

You must provide the project, exact worktree path, expected branch and base branch, mode, approved Issue content or GitHub Issue URL, current PR description or URL, implementation evidence, and any previous blocking findings for re-review.

Can this review workflow modify files or run tests?

No. The workflow is strictly read-only: it cannot modify files, run repository commands, switch branches, commit, push, or merge. Supplied command output is treated as reported evidence, and MCP never runs tests.

What happens when the review finds blocking issues?

The Skill returns a changes-required verdict listing every blocker with the exact file, current fragment, required replacement, and rationale. It then provides one consolidated correction prompt ready for direct use by Copilot or Codex.

Why does the review return an incomplete status instead of a verdict?

When required context cannot be fully read, such as a truncated diff, changed snapshot, missing worktree metadata, or unreadable files, the Skill returns an incomplete-inspection status listing what was checked and what is missing rather than issuing a partial verdict.