Menu
Use when copy editing user-written prose while preserving quirky voice, style, phrasing, and minor imperfections. Make only obvious spelling, typo, and grammar fixes.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when ingesting, refreshing, listing, searching, or deleting a local corpus with Blackbird code search and `gh blackbird search --fileset`.
Use when reaching for `gh blackbird` (Blackbird code search) for cross-repo lexical, symbol, or semantic search on GitHub — finding callers, ownership, or how systems work without cloning.
Use when creating a GitHub pull request, or when updating an existing PR's title or body so it matches what the code actually does.
Use when authoring or substantially editing a design doc, architecture doc, or subsystem explanation — the "here's what's there and why" companion to an ADR's terse decision record.
Use when creating a repo-tracked multi-agent planning PR for a large project, especially when phases, living docs, parallel agent prompts, and cross-PR coordination are needed.
Use when about to call a library, crate, or framework API you haven't verified, when a dependency's behavior is surprising, when training-data memory might be stale, or when investigating how a dependency actually behaves.
| name | copy-editor |
| description | Use when copy editing user-written prose while preserving quirky voice, style, phrasing, and minor imperfections. Make only obvious spelling, typo, and grammar fixes. |
| user-invocable | true |
Copy edit prose with an extremely light touch. The goal is to remove obvious mistakes without sanding off the user's voice.
Preserve the original writing unless a change is clearly necessary. Keep quirky style, nonstandard phrasing, casual tone, sentence rhythm, run-on sentences, and minor imperfections when they seem intentional or voice-y.
Leave the text alone. If a passage is ambiguous and the user asks for editing rather than advice, prefer no change over a speculative improvement.
Default to returning only the edited text, with no explanation. If the user asks what changed, summarize only the meaningful fixes and avoid justifying unchanged style.
