// Multi-perspective PR review procedure. Plan a minimal DAG of specialists scoped to what the PR actually touches, synthesize with a critic, post ONE consolidated comment per verbosity tier. Pull before any structured PR review so the methodology stays consistent.
| name | pr-review |
| description | Multi-perspective PR review procedure. Plan a minimal DAG of specialists scoped to what the PR actually touches, synthesize with a critic, post ONE consolidated comment per verbosity tier. Pull before any structured PR review so the methodology stays consistent. |
| allowed-tools | ["Bash","Read","Glob","Grep"] |
A reusable rubric for reviewing a pull request. Works as an orchestrated
flow (via li o fanout or li o flow) or for a solo reviewer.
Any time you need a structured PR review — OSS contribution evaluation, internal code review, security sign-off, release gate.
| Phase | Action |
|---|---|
| 0. Fetch context | gh pr view + gh pr diff → save to _context/ |
| 1. Discovery | Parallel specialists from closed set (correctness, security, architecture, tests, perf) |
| 2. Discussion | Optional — only if dimensions cross-pollinate |
| 3. Critic synthesis | Reads all findings → critic_final/final_synthesis.md |
| 4. Post comment | ONE consolidated comment per verbosity tier |
APPROVE | APPROVE-WITH-FIXES | REJECT
| Verbosity | Content | Safe for |
|---|---|---|
| none | don't post, synthesis stays local | any |
| brief | ≤10 lines: verdict + top MUST-FIX only | OSS |
| substantive | MUST-FIX + SHOULD-FIX with file:line; omit blind-spots | internal repos |
| full | complete synthesis including blind spots + coverage | private repos only |
li skill security-review — threat-model rubric for security dimensionli skill review — general correctness/quality rubricSee specialist-guide.md for specialist dimensions, severity rubric, synthesis format, CLI examples, and source code reference.
Systematic debug workflow: research → orchestrate agents → escalate. Suggest when: stuck after 2-3 attempts, unfamiliar tooling, tempted to "try random things", or errors don't match documentation.
Plan and execute multi-agent workflows using lionagi's CLI: li o flow (DAG pipelines), li o fanout (parallel workers), and li play (playbook invocations). Use when a task needs multiple agents working in parallel or staged phases.
Author lionagi playbooks — reusable YAML workflow templates that define parametric agent tasks. Playbooks live at ~/.lionagi/playbooks/ and run via li play <name>. Use when: creating reusable workflows, parameterizing agent tasks, or setting up repeatable pipelines.
General-purpose code review checklist. Use when reviewing any code change without a narrower specialization. Complements security-review, pr-review (multi-perspective), and the other review skills — pull this when you need the standard correctness/quality rubric without a specific angle.
Threat-model rubric for a focused security review of a code change. Use when reviewing auth / input validation / crypto / secrets / supply chain, or as the "security" dimension of a multi-perspective PR review. Pull this skill before starting so severity calibration and coverage stay consistent.
Orchestrate multi-play shows: decompose a complex goal into sequential plays (each a li play invocation), gate each output for quality, adapt the plan based on results, and merge work into an integration branch. Shows are first-class entities in Lion Studio with dedicated UI at /shows.