com um clique
SearchExpressionParser
SearchExpressionParser contém 3 skills coletadas de CleanCocoa, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
Spawn five parallel Haiku subagents that each review a target (a document, a codebase, a directory, a single file, or a diff) through a different lens, then return an aggregated summary that surfaces issues multiple reviewers agreed on. Use this skill whenever the user asks for a "comprehensive review", "thorough review", "in-depth review", "deep review", "full review", "broad review", "wide review", "360 review", "multi-angle review", "multi-lens review", "multi-perspective review", "parallel review", "clarity review", "quality review" — or for "5 haiku subagents", "five haiku reviewers", "ask 5 haikus to review X", "five-reviewer pass", or any close variant — even if they don't explicitly name the skill. Also use it when the user wants a broad sweep over something they wrote or built (a doc, a PR, a directory, a feature) and is willing to spend tokens on parallel reviewers in exchange for breadth and cross-checking. Prefer this over a single-pass review whenever the user asks for breadth, multiple perspecti
Orchestrate end-to-end implementation of an OpenSpec change by delegating to dedicated subagents — `spec-implementer` for code, `spec-drift-reviewer` / `code-quality-reviewer` / `test-quality-reviewer` / `security-reviewer` in parallel for review, `spec-syncer` for delta-spec sync — looping until clean, then archiving. Use whenever the user wants to "implement", "apply", "orchestrate", "drive", "ship", or "land" an OpenSpec change end-to-end, or when they reference an /opsx:apply workflow that should run hands-off through review and archival. The orchestrator never writes code itself — it only manages subagents.
Reverse-engineer OpenSpec specifications from an existing codebase. Use this skill when the user wants to generate specs from code, document what code actually does as specifications, perform code archaeology, detect spec drift, or bootstrap an openspec directory from an existing project. Also use when the user says "run spec-gen", "generate specs", "reverse engineer specs", or "check for spec drift".