Perform a comprehensive security review of the current codebase

Security review of changes introduced on a branch compared to a base

Security review of staged changes only (git diff --cached)

'Spec-aligned code review agent. Acts as a dedicated independent reviewer:

Code review response protocol. Loads the obra/superpowers receiving-code-review\

Verify the generated tasks.md covers every requirement in spec.md before

Review completed implementation work and update task status.

Relentless blind-peer reviewer for Gemini 3.1 Pro. Validates every cited thesis and paper via Google Search to detect hallucinations. Generates a 'Scientific Integrity Report' saved directly to Obsidian via shell. Triggers: review paper, peer review, manuscript review, referee report, check integrity, verify citations.

Advanced academic paper writing engine for Gemini 3.1 Pro. Features: 12-agent conceptual pipeline, Google Search citation validation, Obsidian-optimized Markdown (LaTeX + [[links]]), and hierarchical multi-file project structure. Triggers: write paper, academic paper, guide my paper, parse reviews, 寫論文, 學術論文, 引導我寫論文, 審查意見.

Orchestrator for the full academic research pipeline with automated project state tracking. Manages the transition between RESEARCH, WRITE, REVIEW, and PUBLISH states. Features: shell-based file management, automatic YAML frontmatter synchronization (status: active/archived), and wiki-link [[ ]] reference management.

Use when reviewing pull requests, reviewing your own code before committing, or when asked to review code changes. Provides structured analysis with severity categorization, security focus, and optional worktree isolation for safe PR review.

Write the plan before writing the code. Execute it in small batches. Review between batches. This is how you avoid rewriting the same feature three times.

Perform an automated code review on recent changes. Checks for security issues, performance problems, error handling gaps, and code quality. Outputs a structured report with severity levels.

client-prep

Automated weekly self-audit of agent operations, cron health, memory gaps, and process failures. Use when performing periodic reviews, operational health checks, identifying automation gaps, surfacing wrong assumptions, or generating improvement recommendations. Triggers on: weekly review, meta-audit, operations audit, what broke this week, process review, improvement cycle, retrospective, week in review.

Use when analyzing large codebases (>200 lines), performing web searches for current info, or needing adversarial plan reviews.

A cybernetics × AI agent seminar skill. Grounded in *Cybernetics and Scientific Methodology* (Jin Guantao) and Wienerian cybernetics, it analyzes how cybernetic principles inform modern AI agent R&D, architecture review, and design guidance. Trigger when users mention cybernetics, feedback control, agent architecture, systems theory, black-box methods, negative feedback, positive feedback, agent design principles, steady-state systems, information entropy, purposive behavior, functional simulation, or Ashby's law of requisite variety. Also use when users want to review agent architectures from a cybernetic perspective, discuss feedback mechanism design, analyze agent stability and self-evolution, or organize cybernetics × AI agent seminars.

A double-loop learning execution review skill. Reviews the execution history after a task is completed and turns it into a concise retrospective, handoff, or improvement memo. Use this whenever a coding, writing, research, planning, debugging, or operational task has just finished; whenever files, commands, tests, or deliverables were produced; whenever the user asks to summarize what was done, review the execution, create a handoff, capture lessons learned, or prepare for the next iteration; and especially when the user needs not only a summary of what happened, but a judgment about whether the original goal, assumptions, success criteria, or working rules should change before the next pass. If there is execution evidence in the conversation, err on the side of using this skill instead of waiting for the user to ask explicitly.

Use when users want to commit changes, improve a commit message, split mixed changes into logical commits, clean up recent local history, remove accidentally committed files, squash or reword recent local commits, or generally sort out a local Git mess before review or a PR.

Use when users want Excalidraw diagrams, flowcharts, architecture diagrams, sequence diagrams, data-flow diagrams, mind maps, concept maps, or Obsidian `.excalidraw.md` files, especially when they want the diagram reviewed against an exported PNG and refined for layout, connections, and readability.

Pre-launch security audit for web apps. Runs OWASP checks via shell scripts, then AI analyzes findings. Covers rate limiting, hosting bypass, data exposure, headers, session security, AI risks. Complements /security-review.

Comprehensive Seurat v5 (R) guide for single-cell RNA-seq and multimodal analysis. Covers installation, standard workflows (Normalize/SCTransform), clustering, integration (CCA/RPCA/Harmony), differential expression (FindMarkers/FindAllMarkers), visualization (DimPlot/FeaturePlot/VlnPlot/DoHeatmap), spatial transcriptomics (Visium/Visium HD/MERFISH/Slide-seq), CITE-seq, ATAC-seq, WNN, cell cycle regression, hashing/demultiplexing, sketch analysis, BPCells on-disk, pseudobulk, and format conversion. Use this skill whenever writing, debugging, or reviewing Seurat R code, building scRNA-seq pipelines, or looking up Seurat syntax, even for simple questions.

Write emails people actually read. Use when crafting subject lines, structuring email content, writing CTAs, optimizing preview text, or improving open and click rates.

'Author, fix, and review Eraser Diagram-as-Code DSL from natural language requirements using this repository specs. Use this skill whenever the user asks for Eraser DSL, diagram-as-code, flowcharts, ERD/schema diagrams, architecture/cloud diagrams, sequence diagrams, BPMN/swimlane diagrams, syntax fixes, icon/styling updates, or conversion from plain English process/system descriptions into runnable Eraser code.'

Embedded C development, motor control algorithms, Field Oriented Control (FOC), BLDC six-step commutation, sensing topologies, protection design, and STM32G4 hardware acceleration for digital drives. Use this skill when writing or reviewing firmware for PMSM, BLDC, and related motor-drive systems involving SVPWM, Park/Clarke transforms, current/speed/position cascades, sensorless observers (SMO/PLL), signal filtering, and hardware optimizations such as CORDIC and FMAC when justified by timing, determinism, or control-loop workload.

Role-based review system with lite mode for fast reviews and council mode for chaired deliberation. Reviewers speak from their own job function, can disagree with reasons, and the chair decides whether to approve, request changes, defer, or veto.

Use when reviewing a project's architecture for design pattern applicability -- either validating a design document before implementation, or analyzing an existing codebase for pattern improvement opportunities.

Multi-turn verification loop for LaTeX papers via external reasoning model. Each section agent conducts back-and-forth dialogue, pushing back on weak points, and produces structured reports.

Review, create, update, and sync Markdown documentation so it stays accurate, current-state only, code-aligned, concise, and non-duplicative. Use when the user asks to write docs, update README/docs/*.md, sync docs with the codebase, review docs for drift, stale content, overlap, or inconsistent naming, or enforce documentation standards. Do not use for roadmap writing, speculative design, historical writeups, migration narratives, or changelog-style release narration unless the user explicitly asks for them.

Compare actual patient care against guideline recommendations — flag patients who are overdue for review, off-protocol, or missing recommended interventions. Generate structured audit reports with improvement actions. Integrates with Herald-parsed guideline JSONs. Use for clinical governance cycles, quality improvement, or pre-inspection preparation.

Use when the Apple setup flow needs to create or align project .codex/config.toml, official multi-agent runtime settings, and optional MCP integrations for an Apple repository.

Common software architecture patterns, ADR templates, and anti-pattern detection. Supports architectural review, design decisions, and system documentation.

Structured code review criteria for pre-implementation plan review (Critic) and post-implementation security/quality review. Covers security, performance, maintainability, and correctness with severity ratings.

Security vulnerability detection patterns including OWASP Top 10, language-specific vulnerabilities, and remediation guidance. Load when reviewing code for security issues, conducting audits, or implementing authentication/authorization.

TDD workflow and test strategy patterns including test pyramid, coverage strategies, mocking approaches, and anti-patterns. Load when writing tests, designing test strategies, or reviewing test coverage.

Refines ML/scientific LaTeX papers based on reviewer or advisor feedback. Handles structural reorganization (moving problem statements, merging sections), concrete instantiations of abstract tables, cross-file deduplication, and compilation verification. Use when the user requests paper revisions, addresses reviewer comments, restructures sections, or improves exposition clarity.

Draft or revise a mathematically rigorous LaTeX research paper for theory-heavy ML, scientific computing, numerical analysis, control, geometry, or applied mathematics. Use when the user wants help planning the paper, structuring sections, formalizing notation, deciding theorem/proof obligations, specifying complexity or convergence claims, designing figures, or improving global flow and cross-references. Do not use for final QA-only review without drafting or restructuring work.

Review a LaTeX research paper for mathematical rigor, notation consistency, proof obligations, numerical-analysis discipline, complexity claims, convergence/error bounds, figure quality, section flow, cross-references, and global coherence. Use when the user wants a deep technical review or verification pass on a paper, supplement, or LaTeX project. Do not use for initial drafting unless the user explicitly asks for review-first feedback.

Research-Plan-Implement workflow with Codex peer review. Use when the user says /rpi, asks to start a research-plan-implement cycle, wants Codex review on a plan, or needs to create research docs, plans, or implementation reports following the RPI protocol.

Review and fix alignment, label collision, clipping, legend-over-data, overlap, and layout issues in TikZ and pgfplots figures inside LaTeX documents. Use when the user wants to review figures in a paper, tutorial, lecture notes, or thesis before submission; when a reviewer flags figure problems; when a rendered figure visibly has overlap, clipping, or label collisions; when setting up a per-figure review workflow across a large document; or when the user shows a screenshot of a figure that looks wrong. Trigger proactively whenever the user mentions figure alignment, TikZ layout, pgfplots legends/axes, figure cleanup, or asks to fix a figure — even if they don't explicitly say 'review'. Covers a fast iteration loop: extract each tikzpicture into a standalone, compile to PNG, fix, sync back to the main file.

Analyze contracts to identify key clauses, risks, obligations, deadlines, and parties. Multi-language support with focus on French and EU commercial law.

Evaluate AI agent outputs systematically using rubrics, assertions, and reference comparisons. Detect quality drift over time.

Detect and classify technical debt in AI-generated code — patterns specific to LLM outputs, shallow implementations, missing edge cases, and accumulation signals.

Manage skill versioning, freshness tracking, deprecation, changelog generation, and maintenance workflows for skill repository maintainers.

Validate SKILL.md structure, frontmatter completeness, token budget, freshness, naming conventions, and cross-platform portability before publishing.

Use when executing an implementation plan task-by-task - dispatches subagents for implementation, manages git worktrees, handles phased multi-service deployment

Use when starting a software development conversation and the user's intent is not clearly matched by a specific enggenie skill - routes to the right role-based expert

Use when requesting or receiving code review - dispatches reviewer subagent or processes human PR feedback with technical evaluation

Use when reviewing frontend implementation against design specs - design system compliance, responsive behavior, accessibility audit

Use this skill when the user is stuck in a video game and wants help without spoilers. Triggers: 'hintme', 'I'm stuck', 'what do I do next', 'hint me', 'game help', 'stuck in game', 'where do I go', 'how do I beat this', 'game screenshot help'. Analyzes game screenshots and gives progressive hints — nudge first, then clearer direction, then explicit answer. Works with any game. Do NOT use for: game recommendations, game reviews, non-gaming questions, or cheat codes.