pip-skills

Persistent per-repo work ledger: cards, stages, sprints, token budgets, a durable knowledge base of facts, and session resume/handoff. Use when starting a piece of tracked work, when the user asks "what's in flight", "resume where we left off", "start a new card/task", "log progress", to record or recall a durable fact, or at the start of any session in a repo with an overseer state directory (`.workflow/` or `scratch/workflow/`). The state layer beneath the orchestrate skill; drive it through the overseer CLI, never by editing files.

Drive a card of work end-to-end with delegated agents and adversarial review loops: bootstrap, planning, plan gate, implementation, review, verification, merge gate. Use when the user hands over a task to execute under overseer, says "run this card", "orchestrate", "work the backlog", resumes in-flight orchestrated work, or asks to hand over / reset context mid-run. Requires the overseer ledger (invoke overseer:ledger first if the overseer state directory is missing).

Keep vigil over a session's context: measure how full the context window is (ctx NN%) and hand over in-process via /clear at points you choose, resuming from a re-injected handover. Use when the user wants to reset/compact context without losing the thread, asks "how full is my context", "hand over", "reset and resume", or runs a long/unattended session that must manage its own context. Requires tmux for automatic handover; works manually without it.

Use when the user wants to create a new "review-as-X" persona by cloning a reviewer's public GitHub comment history. Triggers on "clone reviewer", "create review persona", "make a reviewer bot for X", "review-clone setup", or the slash command /clone-reviewer.

Use when the user invokes /review-as-<alias>, says "review as <alias>", asks "would <alias> like X", or runs refresh/chat on an existing review-clone persona. Loads PERSONA.md, dispatches to review/refresh/chat mode.

Use when the user wants to audit a Django Python file, view, model, or symbol for ORM performance issues — N+1 queries, missing or composite indexes, bulk-write loops (.save() in loops), over-fetching wide columns, signal-bypassing .update()/bulk_* calls, slow QuerySets, slow admin changelists, slow DRF endpoints, or any Django ORM anti-pattern. Use whenever the user shares a Django file path or dotted symbol alongside performance concerns ("slow", "killing prod", "N+1", "hits the DB once per row", "make X faster", "review queryset", "audit performance", "EXPLAIN this", "optimise queries"). Do NOT use for non-Django code (SQLAlchemy, raw SQL outside the ORM, Flask), schema migrations or column adds, validation/correctness bugs, or tooling setup (Django Debug Toolbar, Silk).

Use when auditing an email template or email codebase for rendering, accessibility, deliverability, and templating violations. Triggers on "audit my email", "check my email template", "review this email", "email audit", "check email compliance", "review for email issues", "audit email templates".

Use when generating a new email template from a description, brief, or specification. Triggers on "generate an email", "create an email template", "write an email for", "scaffold an email", "build an email template", "draft a transactional email", "create order confirmation email", "write welcome email template".

Use when reviewing changed email templates in a PR or branch, or spot-checking a specific email file. Triggers on "check my email PR", "review email changes", "spot-check this template", "email visitation", "audit email diff", "what's wrong with this email", "review this email file".

Use when the user mentions PR comments, PR reviews, bot feedback, review threads, or anything related to GitHub pull request review workflow. Must use for "check my PR", "triage PR feedback", "what did the bot say", "PR progress report", "show all review rounds", "resolve threads", "action PR comments", "full PR history", "what's been fixed so far", "PR progress summary". Use even if the user just says "PR review" or asks about bot review status.

Use when selecting architectural patterns before implementation, planning a phased roadmap, or scanning an existing codebase to generate .architecture/config.yml (discover mode). Triggers on "what patterns should we use", "architect our system", "plan our architecture", "assess our design", or when no config exists yet.

Use when auditing a codebase against architectural doctrine. Triggers on "audit my code", "check architecture", "run doctrines", "review system design", "check pattern compliance".

Use when creating a new architecture doctrine, updating an existing one, or converting informal architecture rules into an auditable format. Triggers on "write a new doctrine", "create a rule set", "add a doctrine", or "update the X doctrine".