ai-engineering-workflow-skills

Run an independent semantic review gate before merging non-trivial work, on top of (not duplicating) Alibaba Code Review and CI. Use after implementation and verification, especially for medium/high-risk changes.

Run a cold-start implementer, reviewer, and fixer subagent chain for one issue, gated by CI, ending in a staging PR. Use when subagent delegation is authorized and the issue is non-trivial.

Add GitHub-visible AI agent and AI code-review metadata without adding AI attribution to commits, and scope Alibaba/Open Code Review's review surface to control LLM token spend. Use when configuring PR templates, PR creation commands, PR update comments, or Alibaba Code Review/open code review workflows to disclose the implementing agent, review tool, LLM model, run URL, or to add/tune a `.opencodereview/rule.json`.

Define acceptance criteria, risk level, and verification before editing. Use at the start of non-trivial implementation or when an issue lacks clear proof of completion.

Use when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the council", get a brutal second opinion before building something, or says "/roast". Spins up a 6-persona council that attacks the idea from every angle, then a Judge returns one GO / RESHAPE / KILL verdict with the cheapest test to de-risk it.

Compact the current conversation into a handover document a fresh agent can pick up and continue seamlessly. Invoke when only 5-10% of the session limit remains, when context usage passes 40% (less than 60% of the context window remaining), when context is about to cross an agent or session boundary, when work is blocked, or on explicit user request — never haphazardly mid-task. Covers decisions, shipped changes, key files, running state, verification, deferrals, and open questions.

Check deployment, staging, rollback, and health verification before release. Use for user-facing, infrastructure, CI/CD, integration, or high-risk changes.

Clarify non-trivial engineering work before implementation by resolving ambiguity, terminology, constraints, and the smallest viable path. Use when a request is broad, fuzzy, architectural, cross-cutting, or has hidden product decisions.

Break high-level work into independently executable GitHub issues using vertical slices. Use when a plan, PRD, roadmap item, or vague feature needs issue-sized execution units.

Convert human-only blockers into visible GitHub issues. Use when work is blocked by missing credentials, secrets, DNS, billing, account permissions, approvals, or other user-held external state.