What is the difference between the Claude and Codex phases?

Phase 1 uses Claude for initial self-review, while Phase 2 uses Codex for cross-validation to identify nuanced issues Claude might have missed, providing a double-layered quality check.

Can I control how much content is changed?

Yes, you can trigger 'aggressive' mode for significant trimming and conciseness, or 'conservative' mode for minimal changes that only fix clear errors.

What file types does it support?

It auto-detects and supports Markdown (.md), project plans, configuration files (JSON, YAML, TOML), source code (TS, JS, PY, etc.), and general prose.

How does it handle ambiguous instructions or TODOs?

In Phase 3, the skill enters an Interactive Resolution mode where it presents options to the user to clarify vague sections rather than making subjective assumptions.

Does Doc Polisher change my file format?

No, it follows the principle of in-place enhancement, meaning it fixes content issues while strictly preserving the original file structure and formatting.

Doc Polisher

Name: Doc Polisher
Author: fiatkongen

byfiatkongen

内容管理

Refines and polishes documents through iterative multi-phase review loops to improve clarity, consistency, and professional formatting.

关于

Doc Polisher is a specialized Claude Code skill designed for high-fidelity document refinement without altering original file structures or authorial voice. It employs a rigorous three-phase workflow: a Claude self-review loop for internal logic, a Codex cross-validation loop to catch missed nuances, and an interactive phase for resolving user-specific ambiguities. Whether fixing inconsistent terminology, removing redundancies, or cleaning up formatting across Markdown, configuration files, or code comments, Doc Polisher ensures professional-grade output while strictly adhering to user-defined constraints like aggressive or conservative editing modes.

主要功能

In-place enhancement that preserves original file structure and style
Three-phase review process involving Claude, Codex, and user verification
Auto-detection and specialized handling for Markdown, code, config, and prose
Intelligent resolution of inconsistent terminology and broken internal references
0 GitHub stars
Configurable editing modes including Aggressive (concise) and Conservative (minimal changes)

使用场景

Polishing configuration files and code comments for consistency before a major release
Standardizing technical documentation and README files across a large repository
Cleaning up redundant prose and fixing broken links in project plans or wikis

关于

主要功能

In-place enhancement that preserves original file structure and style
Three-phase review process involving Claude, Codex, and user verification
Auto-detection and specialized handling for Markdown, code, config, and prose
Intelligent resolution of inconsistent terminology and broken internal references
0 GitHub stars
Configurable editing modes including Aggressive (concise) and Conservative (minimal changes)

使用场景

Polishing configuration files and code comments for consistency before a major release
Standardizing technical documentation and README files across a large repository
Cleaning up redundant prose and fixing broken links in project plans or wikis