メニュー
Remove AI-generated slop from code changes. Use when the user says "deslop", "remove slop", "clean up AI comments", or wants to strip unnecessary AI-added comments from a branch's diff. Works with any language, optimized for Go and Zig codebases.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Comprehensive Zig code review across all quality dimensions. Triggers on /zig-review. Runs parallel subagents — each using an existing skill — for Tiger Style compliance, Zig 0.15 idiom correctness, deslop, simplification opportunities, and API design quality. Always operates on the full branch diff against main. Report-only: never makes changes.
TigerBeetle's coding style guide for writing safe, performant Zig code. Enforces strict safety rules (assertions, bounded control flow, static memory), performance discipline (mechanical sympathy, batching), and naming/formatting conventions. Use this skill when: (1) Writing or generating Zig code — apply Tiger Style rules during generation, (2) Reviewing Zig code — run a detailed review against all Tiger Style principles, (3) User asks about Tiger Style conventions, naming, assertions, or formatting. Triggers on: writing Zig code, code review requests, style questions, "tiger style", "tiger review".
Write correct, idiomatic Zig 0.15 code. Use when writing new Zig code, editing existing Zig files, debugging Zig compilation errors, reviewing Zig code, or working with build.zig files. Triggers on any task involving .zig files. Critical: LLM training data contains outdated Zig patterns (0.11-0.13) that will produce broken code — this skill provides the current 0.15 patterns.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Write concise git commit messages and commit staged changes. Trigger when the user says "commit this", "commit that", "make a commit", "commit the changes", or any instruction to create a git commit. Do NOT auto-stage files — only commit what is already staged.
Work within Nix flake-based devShells. Use when working in any project that has a flake.nix, when commands fail due to missing tools, when dependencies need to be added or removed, or when setting up a development environment. Triggers on flake.nix presence, missing command errors, or dependency management tasks. IMPORTANT — always prefer the devShell over installing tools globally or via pip/npm/brew.
| name | deslop |
| description | Remove AI-generated slop from code changes. Use when the user says "deslop", "remove slop", "clean up AI comments", or wants to strip unnecessary AI-added comments from a branch's diff. Works with any language, optimized for Go and Zig codebases. |
Check the diff against main and remove all AI-generated comment slop introduced in this branch.
LLMs compulsively insert "section divider" comments to organize code into labeled regions. These are the single biggest tell of AI-generated code. Remove them aggressively. They add no information — the code structure is the organization.
Patterns to match (any comment syntax: //, #, /* */, --, etc.):
// --- Tests ---, // === Helpers ===, # ---- Config ----// Tests, // Helpers, // Public API, // Private methods// --- Re-exports: foo.zig ---, // --- Sub-modules ---// Write helpers, // Utility functions, // Constants, // Type definitionsIf the pre-existing code already uses section headers in this style, leave them alone — only strip ones introduced in this branch's diff.
// initialize the variable, // return the result)// processItems processes items)// check if error, // loop through items)git diff main