Paste a git diff and get a PR description, a changelog entry, and reviewer-risk callouts that name the file, what could break, and what to check. Only flags backed by the diff, and "no elevated-risk patterns found" when there are none. Built for AI-sized PRs.
Verify a versioned software release is genuinely complete — tickets actually implemented (not just closed), docs discoverable (not just present), CI green on all matrix platforms, coverage gated, security scan clean, rollback path tested, and version metadata consistent. Produces a structured READY / NOT READY / BLOCKED report with evidence-backed findings and action items.
Before you write code, kill the causes of rework. A phase-gate skill that runs a pre-implementation diagnosis (clarify requirements, success criteria, non-goals, hidden risks) and sets up the dev environment (toolchain check, repo init, dependency/secret/config templates, DB/API contract, folder layout). Each gate must pass before moving on. Delivers a diagnosis report, a stack-selection doc, and a ready-to-build foundation to hand off to implementation.
Three AI reviewers cross-examine a backlog item for thin user value, hidden effort, and roadmap misfit before you commit a sprint to it.
Guides, a 56-item checklist, a ready PR template, and a fill-in team policy for code review culture. Includes 10 good/bad comment pairs and 30 situational review comments, unified by a blocker/suggestion/nit/question/praise severity system.
I've managed thousands of pull requests across open-source and enterprise repos — branching strategies, CI debugging, merge conflicts, and review workflows. This skill encodes that entire pipeline so you can automate your PR lifecycle through natural language, just tell me what you need.
比較前後版本清單與依賴關係，找出變更影響及需要重審的項目。Compare declared revision dependencies and identify reviews needing renewal. Local Python download; no model required.
You have an R&R decision, two reviewer reports pulling in different directions, and a manuscript to revise. The hardest part isn't the revisions; it's the response letter. Capitulate and you weaken the paper. Push back and you alienate the editor. This agent drafts the letter the editor needs: an opening that names the substantive changes, a point-by-point response with page references for every change, and principled pushback where a reviewer request would weaken the argument.
Paste PostgreSQL migration SQL, an ORM migration, or a PR diff. Get a PASS/REVISE/BLOCK review with statement-level lock and rewrite risks, safer DDL, zero-downtime rollout steps, rollback boundaries, monitoring SQL, and a paste-ready PR comment.