de-ai-flavor
De-AI-Flavor Skill
Trigger
- Keywords: de-ai, remove AI traces, humanize document, de-ai-flavor, humanize
When NOT to Use
- Co-Authored-By in CHANGELOG (Git convention)
- Documents discussing AI technology (topic itself requires it)
- Quoting others' AI-related content
- Variable/function names in code
Usage
/de-ai-flavor docs/xxx.md # Process specified file
/de-ai-flavor docs/ # Process all .md in directory
/de-ai-flavor # Process .md in git diff
Detection Rules
| Type | Pattern | Action |
|---|---|---|
| Tool names | Claude/Codex/GPT/AI assistant | Remove |
| Boilerplate | "Let me...", "First...then...", "In conclusion" | Rewrite |
| Over-structuring | One sentence per heading, too many #### levels | Simplify |
| Service tone | "Hope this helps", "If you have questions..." | Remove |
| Self-description | "Next I will...", "I will proceed to..." | Remove |
| Iteration leaks | "Round 1/Round 2/Round N" | Rewrite |
Workflow
Scan file -> Mark AI traces -> Remove/Rewrite/Simplify -> Output summary
Verification
- All tool names removed
- Boilerplate rewritten to natural tone
- Structure not overly flat or nested
Output Format
## De-AI-Flavor Results
**File**: `docs/xxx.md`
| Line | Original | Change | Reason |
| ---- | --------------------- | ----------------------- | ---------------- |
| 15 | Let me explain... | Removed | AI self-description |
| 32 | Claude suggests... | Changed to "Suggest..." | Tool name |
**Stats**: Removed 3 tool names | Rewrote 5 boilerplate | Simplified 2 structures
Examples
Input: /de-ai-flavor docs/tech-spec.md
Action: Scan -> Remove "Claude suggests" -> Rewrite "Let me explain" -> Output summary
Input: This document feels very AI-generated, please clean it up
Action: Detect git diff -> Mark AI traces -> Batch process -> Output stats
More from sd0xdev/sd0x-dev-flow
statusline-config
Customize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color scheme', wants to add/remove/change segments (cost, git, model, context), switch color themes (catppuccin, dracula, nord), or asks what can be shown in the statusline.
52tech-spec
Tech spec generation and review. Use when: designing features, writing specs, spec review. Not for: requirements analysis (use req-analyze), implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document.
45codex-brainstorm
Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.
7security-review
Security review via Codex MCP. Use when: OWASP Top 10 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
7test-review
Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
7post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
6