lionagi

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.

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.

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.

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.

Mid-session context capture and proactive decision/pattern capture. Use when: significant progress made but session continues, approaching context limits, switching topics, checkpoint learnings, significant decisions made, patterns emerge, or session is winding down. Lighter than a full session summary — captures progress and continues.

Guide test-driven development workflow. Suggest when: "test first", "TDD", "write tests before", "red green refactor" mentioned, or when implementing features or bug fixes where a test-first approach is beneficial. Enforces Red-Green-Refactor cycle.

Conventional Commits style guide + safety rules. Pull this before any git commit so the message shape and staging rules stay consistent.

Minimal example — verify `li skill` prints the body.