Review code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.

Designs, authors, refactors, and hardens production-grade Cloud Firestore Security Rules (firestore.rules). Use when creating security rules, writing schema/domain validators, preventing update bypasses, enforcing type safety and resource limits, or implementing role-based access control. Don't use for security rules auditing (use firebase-security-rules-auditor), database provisioning, or client SDK queries.

Includes Printing Press, Printing Press Amend, Printing Press Import, Printing Press Output Review, Printing Press Polish, Printing Press Publish, Printing Press Reprint, Printing Press Retro, Printing Press Score

Convert .NET tests from NUnit 3/4 to MSTest v4 while preserving VSTest or MTP. Use for replacing NUnit/NUnit3TestAdapter packages, Test/TestCase/ TestCaseSource/Values attributes, constraint assertions, SetUp/TearDown, OneTimeSetUp, SetUpFixture, FixtureLifeCycle, TestContext, categories, retries, timeouts, and NUnit parallelization. Also use when a "convert NUnit to MSTest" request may already be migrated: inspect and report the no-op. Do not use for NUnit version upgrades, xUnit/TUnit conversion, MSTest upgrades, or runner-only VSTest-to-MTP migration.

EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

Includes Agy Delegate, Aider Delegate, Claude Delegate, Cline Delegate, Codex Delegate, Commandcode Delegate, Copilot Delegate, Cursor Delegate, Delegate Setup, Grok Delegate, Kimi Delegate, Omp Delegate, Opencode Delegate, Pi Delegate, Qoder Delegate, Vibe Delegate, Warp Delegate, Zcode Delegate

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.

Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64/128/256/512, or platform hardware intrinsics; reviewing existing SIMD code, including Vector<T>, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.

Includes Skill Inspector

Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side

Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for printed-CLI polish or a single-CLI fix.

Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish SKILL.md during the diagnostic loop. Not for direct user invocation — its actionable wrappers are /printing-press and /printing-press-polish.

Includes Ponytail, Ponytail Audit, Ponytail Debt, Ponytail Gain, Ponytail Help, Ponytail Review

Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.

Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.

Includes Om Approve Merge Pr, Om Auto Continue Pr, Om Auto Continue Pr Loop, Om Auto Create Pr, Om Auto Create Pr Loop, Om Auto Fix Issue, Om Auto Fix Pr, Om Auto Implement Spec, Om Auto Manage Issues, Om Auto Qa Pr, Om Auto Review Pr, Om Auto Update Changelog, Om Auto Write Spec, Om Backlog, Om Brainstorm, Om Check And Commit, Om Close Fixed Issues, Om Code Review, Om Create Skill, Om Discover, Om Followup Issue From Pr, Om Integration Tests, Om Merge Buddy, Om Mockup Prototype, Om Open Pr, Om Pipeline Retro, Om Pr Autopilot, Om Prepare Issue, Om Prepare Test Env, Om Review Prs, Om Root Cause, Om Setup Agent Pipeline, Om Setup Discovery Pipeline, Om Spec Writing, Om Synthetic Users, Om Ux Review Pr, Om Ux Setup, Om Ux Shape, Om Verify In Repo

Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.

Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.

Includes Earnings Analysis, Initiating Coverage

Refresh the repo's captured learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless the learnings store is explicit.

Resolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.

Review one practical document and report tiered editorial feedback (what a common edit, a copy edit, and a full substantive pass would each change) without modifying the document and without numeric scores. Read-only. Use when asked to review, critique, give feedback, or get an edit plan, and you do not want edits applied, a scored eval, or a version comparison.

Includes Autoplan, Benchmark, Benchmark Models, Browse, Canary, Careful, Codex, Context Restore, Context Save, Cso, Design Consultation, Design Html, Design Review, Design Shotgun, Devex Review, Diagram, Document Generate, Document Release, Freeze, Gstack Openclaw Ceo Review, Gstack Openclaw Investigate, Gstack Openclaw Office Hours, Gstack Openclaw Retro, Gstack Upgrade, Guard, Hackernews Frontpage, Health, Investigate, Ios Clean, Ios Design Review, Ios Fix, Ios Qa, Ios Sync, Land And Deploy, Learn, Make Pdf, Office Hours, Open Gstack Browser, Pair Agent, Plan Ceo Review, Plan Design Review, Plan Devex Review, Plan Eng Review, Plan Tune, Qa, Qa Only, Retro, Review, Scrape, Setup Browser Cookies, Setup Deploy, Setup Gbrain, Ship, Skillify, Spec, Sync Gbrain, Unfreeze

Delegate a coding task to the Pi coding agent CLI (`pi`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Pi - phrasings like "have Pi implement X", "delegate this to pi", "run it through Pi", or "use pi to implement/fix/refactor" - or wants to run a queue of coding tasks through Pi while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Delegate a coding task to Oh My Pi (`omp`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Oh My Pi / omp - phrasings like "have omp implement X", "delegate this to oh my pi", "run it through omp", "use oh-my-pi to implement/fix/refactor" - or wants to run a queue of coding tasks through omp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or when they mean the original Pi CLI (`pi`) — that is pi-delegate.

Delegate a coding task to the Google Antigravity CLI (`agy`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Includes Api And Interface Design, Browser Testing With Devtools, Ci Cd And Automation, Code Simplification, Constraint Driven Development, Context Engineering, Debugging And Error Recovery, Deprecation And Migration, Documentation And Adrs, Idea Refine, Interview Me, Source Driven Development, Spec Driven Development

Review code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.

Designs, authors, refactors, and hardens production-grade Cloud Firestore Security Rules (firestore.rules). Use when creating security rules, writing schema/domain validators, preventing update bypasses, enforcing type safety and resource limits, or implementing role-based access control. Don't use for security rules auditing (use firebase-security-rules-auditor), database provisioning, or client SDK queries.

Includes Printing Press, Printing Press Amend, Printing Press Import, Printing Press Output Review, Printing Press Polish, Printing Press Publish, Printing Press Reprint, Printing Press Retro, Printing Press Score

Convert .NET tests from NUnit 3/4 to MSTest v4 while preserving VSTest or MTP. Use for replacing NUnit/NUnit3TestAdapter packages, Test/TestCase/ TestCaseSource/Values attributes, constraint assertions, SetUp/TearDown, OneTimeSetUp, SetUpFixture, FixtureLifeCycle, TestContext, categories, retries, timeouts, and NUnit parallelization. Also use when a "convert NUnit to MSTest" request may already be migrated: inspect and report the no-op. Do not use for NUnit version upgrades, xUnit/TUnit conversion, MSTest upgrades, or runner-only VSTest-to-MTP migration.

EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

Includes Agy Delegate, Aider Delegate, Claude Delegate, Cline Delegate, Codex Delegate, Commandcode Delegate, Copilot Delegate, Cursor Delegate, Delegate Setup, Grok Delegate, Kimi Delegate, Omp Delegate, Opencode Delegate, Pi Delegate, Qoder Delegate, Vibe Delegate, Warp Delegate, Zcode Delegate

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.

Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64/128/256/512, or platform hardware intrinsics; reviewing existing SIMD code, including Vector<T>, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.

Includes Skill Inspector

Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side

Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for printed-CLI polish or a single-CLI fix.

Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish SKILL.md during the diagnostic loop. Not for direct user invocation — its actionable wrappers are /printing-press and /printing-press-polish.

Includes Ponytail, Ponytail Audit, Ponytail Debt, Ponytail Gain, Ponytail Help, Ponytail Review

Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.

Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.

Includes Om Approve Merge Pr, Om Auto Continue Pr, Om Auto Continue Pr Loop, Om Auto Create Pr, Om Auto Create Pr Loop, Om Auto Fix Issue, Om Auto Fix Pr, Om Auto Implement Spec, Om Auto Manage Issues, Om Auto Qa Pr, Om Auto Review Pr, Om Auto Update Changelog, Om Auto Write Spec, Om Backlog, Om Brainstorm, Om Check And Commit, Om Close Fixed Issues, Om Code Review, Om Create Skill, Om Discover, Om Followup Issue From Pr, Om Integration Tests, Om Merge Buddy, Om Mockup Prototype, Om Open Pr, Om Pipeline Retro, Om Pr Autopilot, Om Prepare Issue, Om Prepare Test Env, Om Review Prs, Om Root Cause, Om Setup Agent Pipeline, Om Setup Discovery Pipeline, Om Spec Writing, Om Synthetic Users, Om Ux Review Pr, Om Ux Setup, Om Ux Shape, Om Verify In Repo

Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.

Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.

Includes Earnings Analysis, Initiating Coverage

Refresh the repo's captured learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless the learnings store is explicit.

Resolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.

Review one practical document and report tiered editorial feedback (what a common edit, a copy edit, and a full substantive pass would each change) without modifying the document and without numeric scores. Read-only. Use when asked to review, critique, give feedback, or get an edit plan, and you do not want edits applied, a scored eval, or a version comparison.

Includes Autoplan, Benchmark, Benchmark Models, Browse, Canary, Careful, Codex, Context Restore, Context Save, Cso, Design Consultation, Design Html, Design Review, Design Shotgun, Devex Review, Diagram, Document Generate, Document Release, Freeze, Gstack Openclaw Ceo Review, Gstack Openclaw Investigate, Gstack Openclaw Office Hours, Gstack Openclaw Retro, Gstack Upgrade, Guard, Hackernews Frontpage, Health, Investigate, Ios Clean, Ios Design Review, Ios Fix, Ios Qa, Ios Sync, Land And Deploy, Learn, Make Pdf, Office Hours, Open Gstack Browser, Pair Agent, Plan Ceo Review, Plan Design Review, Plan Devex Review, Plan Eng Review, Plan Tune, Qa, Qa Only, Retro, Review, Scrape, Setup Browser Cookies, Setup Deploy, Setup Gbrain, Ship, Skillify, Spec, Sync Gbrain, Unfreeze

Delegate a coding task to the Pi coding agent CLI (`pi`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Pi - phrasings like "have Pi implement X", "delegate this to pi", "run it through Pi", or "use pi to implement/fix/refactor" - or wants to run a queue of coding tasks through Pi while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Delegate a coding task to Oh My Pi (`omp`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Oh My Pi / omp - phrasings like "have omp implement X", "delegate this to oh my pi", "run it through omp", "use oh-my-pi to implement/fix/refactor" - or wants to run a queue of coding tasks through omp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or when they mean the original Pi CLI (`pi`) — that is pi-delegate.

Delegate a coding task to the Google Antigravity CLI (`agy`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Includes Api And Interface Design, Browser Testing With Devtools, Ci Cd And Automation, Code Simplification, Constraint Driven Development, Context Engineering, Debugging And Error Recovery, Deprecation And Migration, Documentation And Adrs, Idea Refine, Interview Me, Source Driven Development, Spec Driven Development

Review code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.

Designs, authors, refactors, and hardens production-grade Cloud Firestore Security Rules (firestore.rules). Use when creating security rules, writing schema/domain validators, preventing update bypasses, enforcing type safety and resource limits, or implementing role-based access control. Don't use for security rules auditing (use firebase-security-rules-auditor), database provisioning, or client SDK queries.

Includes Printing Press, Printing Press Amend, Printing Press Import, Printing Press Output Review, Printing Press Polish, Printing Press Publish, Printing Press Reprint, Printing Press Retro, Printing Press Score

Convert .NET tests from NUnit 3/4 to MSTest v4 while preserving VSTest or MTP. Use for replacing NUnit/NUnit3TestAdapter packages, Test/TestCase/ TestCaseSource/Values attributes, constraint assertions, SetUp/TearDown, OneTimeSetUp, SetUpFixture, FixtureLifeCycle, TestContext, categories, retries, timeouts, and NUnit parallelization. Also use when a "convert NUnit to MSTest" request may already be migrated: inspect and report the no-op. Do not use for NUnit version upgrades, xUnit/TUnit conversion, MSTest upgrades, or runner-only VSTest-to-MTP migration.

EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

Includes Agy Delegate, Aider Delegate, Claude Delegate, Cline Delegate, Codex Delegate, Commandcode Delegate, Copilot Delegate, Cursor Delegate, Delegate Setup, Grok Delegate, Kimi Delegate, Omp Delegate, Opencode Delegate, Pi Delegate, Qoder Delegate, Vibe Delegate, Warp Delegate, Zcode Delegate

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.

Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64/128/256/512, or platform hardware intrinsics; reviewing existing SIMD code, including Vector<T>, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.

Includes Skill Inspector

Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side

Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for printed-CLI polish or a single-CLI fix.

Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish SKILL.md during the diagnostic loop. Not for direct user invocation — its actionable wrappers are /printing-press and /printing-press-polish.

Includes Ponytail, Ponytail Audit, Ponytail Debt, Ponytail Gain, Ponytail Help, Ponytail Review

Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.

Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.

Includes Om Approve Merge Pr, Om Auto Continue Pr, Om Auto Continue Pr Loop, Om Auto Create Pr, Om Auto Create Pr Loop, Om Auto Fix Issue, Om Auto Fix Pr, Om Auto Implement Spec, Om Auto Manage Issues, Om Auto Qa Pr, Om Auto Review Pr, Om Auto Update Changelog, Om Auto Write Spec, Om Backlog, Om Brainstorm, Om Check And Commit, Om Close Fixed Issues, Om Code Review, Om Create Skill, Om Discover, Om Followup Issue From Pr, Om Integration Tests, Om Merge Buddy, Om Mockup Prototype, Om Open Pr, Om Pipeline Retro, Om Pr Autopilot, Om Prepare Issue, Om Prepare Test Env, Om Review Prs, Om Root Cause, Om Setup Agent Pipeline, Om Setup Discovery Pipeline, Om Spec Writing, Om Synthetic Users, Om Ux Review Pr, Om Ux Setup, Om Ux Shape, Om Verify In Repo

Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.

Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.

Includes Earnings Analysis, Initiating Coverage

Refresh the repo's captured learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless the learnings store is explicit.

Resolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.

Review one practical document and report tiered editorial feedback (what a common edit, a copy edit, and a full substantive pass would each change) without modifying the document and without numeric scores. Read-only. Use when asked to review, critique, give feedback, or get an edit plan, and you do not want edits applied, a scored eval, or a version comparison.

Includes Autoplan, Benchmark, Benchmark Models, Browse, Canary, Careful, Codex, Context Restore, Context Save, Cso, Design Consultation, Design Html, Design Review, Design Shotgun, Devex Review, Diagram, Document Generate, Document Release, Freeze, Gstack Openclaw Ceo Review, Gstack Openclaw Investigate, Gstack Openclaw Office Hours, Gstack Openclaw Retro, Gstack Upgrade, Guard, Hackernews Frontpage, Health, Investigate, Ios Clean, Ios Design Review, Ios Fix, Ios Qa, Ios Sync, Land And Deploy, Learn, Make Pdf, Office Hours, Open Gstack Browser, Pair Agent, Plan Ceo Review, Plan Design Review, Plan Devex Review, Plan Eng Review, Plan Tune, Qa, Qa Only, Retro, Review, Scrape, Setup Browser Cookies, Setup Deploy, Setup Gbrain, Ship, Skillify, Spec, Sync Gbrain, Unfreeze

Delegate a coding task to the Pi coding agent CLI (`pi`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Pi - phrasings like "have Pi implement X", "delegate this to pi", "run it through Pi", or "use pi to implement/fix/refactor" - or wants to run a queue of coding tasks through Pi while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Delegate a coding task to Oh My Pi (`omp`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Oh My Pi / omp - phrasings like "have omp implement X", "delegate this to oh my pi", "run it through omp", "use oh-my-pi to implement/fix/refactor" - or wants to run a queue of coding tasks through omp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or when they mean the original Pi CLI (`pi`) — that is pi-delegate.

Delegate a coding task to the Google Antigravity CLI (`agy`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Includes Api And Interface Design, Browser Testing With Devtools, Ci Cd And Automation, Code Simplification, Constraint Driven Development, Context Engineering, Debugging And Error Recovery, Deprecation And Migration, Documentation And Adrs, Idea Refine, Interview Me, Source Driven Development, Spec Driven Development

Review code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.

Designs, authors, refactors, and hardens production-grade Cloud Firestore Security Rules (firestore.rules). Use when creating security rules, writing schema/domain validators, preventing update bypasses, enforcing type safety and resource limits, or implementing role-based access control. Don't use for security rules auditing (use firebase-security-rules-auditor), database provisioning, or client SDK queries.

Includes Printing Press, Printing Press Amend, Printing Press Import, Printing Press Output Review, Printing Press Polish, Printing Press Publish, Printing Press Reprint, Printing Press Retro, Printing Press Score

Convert .NET tests from NUnit 3/4 to MSTest v4 while preserving VSTest or MTP. Use for replacing NUnit/NUnit3TestAdapter packages, Test/TestCase/ TestCaseSource/Values attributes, constraint assertions, SetUp/TearDown, OneTimeSetUp, SetUpFixture, FixtureLifeCycle, TestContext, categories, retries, timeouts, and NUnit parallelization. Also use when a "convert NUnit to MSTest" request may already be migrated: inspect and report the no-op. Do not use for NUnit version upgrades, xUnit/TUnit conversion, MSTest upgrades, or runner-only VSTest-to-MTP migration.

EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

Includes Agy Delegate, Aider Delegate, Claude Delegate, Cline Delegate, Codex Delegate, Commandcode Delegate, Copilot Delegate, Cursor Delegate, Delegate Setup, Grok Delegate, Kimi Delegate, Omp Delegate, Opencode Delegate, Pi Delegate, Qoder Delegate, Vibe Delegate, Warp Delegate, Zcode Delegate

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.

Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64/128/256/512, or platform hardware intrinsics; reviewing existing SIMD code, including Vector<T>, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.

Includes Skill Inspector

Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side

Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for printed-CLI polish or a single-CLI fix.

Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish SKILL.md during the diagnostic loop. Not for direct user invocation — its actionable wrappers are /printing-press and /printing-press-polish.

Includes Ponytail, Ponytail Audit, Ponytail Debt, Ponytail Gain, Ponytail Help, Ponytail Review

Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.

Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.

Includes Om Approve Merge Pr, Om Auto Continue Pr, Om Auto Continue Pr Loop, Om Auto Create Pr, Om Auto Create Pr Loop, Om Auto Fix Issue, Om Auto Fix Pr, Om Auto Implement Spec, Om Auto Manage Issues, Om Auto Qa Pr, Om Auto Review Pr, Om Auto Update Changelog, Om Auto Write Spec, Om Backlog, Om Brainstorm, Om Check And Commit, Om Close Fixed Issues, Om Code Review, Om Create Skill, Om Discover, Om Followup Issue From Pr, Om Integration Tests, Om Merge Buddy, Om Mockup Prototype, Om Open Pr, Om Pipeline Retro, Om Pr Autopilot, Om Prepare Issue, Om Prepare Test Env, Om Review Prs, Om Root Cause, Om Setup Agent Pipeline, Om Setup Discovery Pipeline, Om Spec Writing, Om Synthetic Users, Om Ux Review Pr, Om Ux Setup, Om Ux Shape, Om Verify In Repo

Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.

Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.

Includes Earnings Analysis, Initiating Coverage

Refresh the repo's captured learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless the learnings store is explicit.

Resolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.

Review one practical document and report tiered editorial feedback (what a common edit, a copy edit, and a full substantive pass would each change) without modifying the document and without numeric scores. Read-only. Use when asked to review, critique, give feedback, or get an edit plan, and you do not want edits applied, a scored eval, or a version comparison.

Includes Autoplan, Benchmark, Benchmark Models, Browse, Canary, Careful, Codex, Context Restore, Context Save, Cso, Design Consultation, Design Html, Design Review, Design Shotgun, Devex Review, Diagram, Document Generate, Document Release, Freeze, Gstack Openclaw Ceo Review, Gstack Openclaw Investigate, Gstack Openclaw Office Hours, Gstack Openclaw Retro, Gstack Upgrade, Guard, Hackernews Frontpage, Health, Investigate, Ios Clean, Ios Design Review, Ios Fix, Ios Qa, Ios Sync, Land And Deploy, Learn, Make Pdf, Office Hours, Open Gstack Browser, Pair Agent, Plan Ceo Review, Plan Design Review, Plan Devex Review, Plan Eng Review, Plan Tune, Qa, Qa Only, Retro, Review, Scrape, Setup Browser Cookies, Setup Deploy, Setup Gbrain, Ship, Skillify, Spec, Sync Gbrain, Unfreeze

Delegate a coding task to the Pi coding agent CLI (`pi`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Pi - phrasings like "have Pi implement X", "delegate this to pi", "run it through Pi", or "use pi to implement/fix/refactor" - or wants to run a queue of coding tasks through Pi while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Delegate a coding task to Oh My Pi (`omp`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Oh My Pi / omp - phrasings like "have omp implement X", "delegate this to oh my pi", "run it through omp", "use oh-my-pi to implement/fix/refactor" - or wants to run a queue of coding tasks through omp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or when they mean the original Pi CLI (`pi`) — that is pi-delegate.

Delegate a coding task to the Google Antigravity CLI (`agy`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Includes Api And Interface Design, Browser Testing With Devtools, Ci Cd And Automation, Code Simplification, Constraint Driven Development, Context Engineering, Debugging And Error Recovery, Deprecation And Migration, Documentation And Adrs, Idea Refine, Interview Me, Source Driven Development, Spec Driven Development