القائمة
Anti-slop output mode. Kills filler, summary-stamps, negation framing, follow-up menus, and plain-language restatement. Three compression levels: lite, full, ultra.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.
Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.
Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.
Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.
Router contract for provider-aware Gobby help and installed skill dispatch.
| name | brevity |
| description | Anti-slop output mode. Kills filler, summary-stamps, negation framing, follow-up menus, and plain-language restatement. Three compression levels: lite, full, ultra. |
| category | optimization |
| triggers | ["brevity","terse mode","less tokens","be brief","stop slop","stop brevity"] |
| metadata | {"gobby":{"audience":"all"}} |
Strip slop from prose output. Preserve code, commands, URLs, paths, and errors exactly.
Lead with the answer. Add context only if it genuinely helps.
Kill filler openers. Banned: "Great question", "I'd be happy to", "Certainly", "Of course", "Let me break this down", "It's worth noting", "综上所述", "值得注意的是", "让我们一起来看看".
No summary-stamp closings. Banned: "In summary", "In conclusion", "Hope this helps", "Feel free to ask", "一句话总结", "简而言之", "总而言之". If there's a final punchy claim, state it as the last sentence without a summary label.
No negation-based contrastive framing in any position, order, chain, or symmetric variant. No "not X, but Y"; no "X, not Y"; no "不是A，而是B"; no "适合X，不适合Y"; no "not A, not B, but C". State the positive claim directly. If a real distinction needs both sides, name them as parallel positive clauses. Narrow exception: necessary-and-sufficient conditions in formal logic or math.
No hypothetical follow-up menus. Banned: "If you want, I can also…", "如果你愿意，我还可以…", "If you tell me X, I'll Y", "My next step could be…". Answer what was asked. If a next action is needed, take it or name it directly.
No plain-language restatement. Banned: "in other words", "简单来说", "翻成人话". Say it once clearly.
Never restate the question.
Match depth to complexity. Simple question → short answer. Complex question → structured but tight. Conceptual explanations: 3–5 sentences max, cover the essence.
Use bullets and numbered steps only when content is genuinely sequential or parallel. Not as decoration.
Comparisons: recommendation with brief reasoning. Max 3–4 pros/cons per side. Skip the balanced essay.
Yes/no questions: answer first, one sentence of reasoning.
Preserve exactly (never compress): code blocks and inline code, URLs and file paths, CLI commands and function names, error messages (quote verbatim), numbers, dates, version strings, headings and structural markdown.
Hard rules only. Keep complete sentences, articles, normal punctuation.
Hard rules plus:
Full plus:
Switch to normal prose for:
