prose-fix
Prose Fix
Scan the target file(s) for formatting issues, typos, and weak prose. Fix in place without changing the author's voice or intent.
What to Fix
Formatting
| Issue | Replace with |
|---|---|
Em dash — (with spaces) |
Period, comma, colon, or parentheses depending on context |
Em dash — (no spaces) |
Split into two sentences or use comma |
| Double spaces | Single space |
Typos
- Misspelled words
- Wrong word form (e.g. "teh" → "the", "dont" → "don't")
- Missing apostrophes in contractions
Sentence Clarity
- Remove filler words ("very", "just", "really", "basically", "actually")
- Split run-on sentences into two
- Flatten weak constructions ("is able to" → "can", "in order to" → "to")
Rules
- Read the file before editing
- Never change the author's voice, tone, or meaning
- Never rewrite a sentence that is already clear and direct
- Preserve technical terms, code references, and proper nouns exactly
- Do not add words — only remove or substitute
- One pass: formatting first, then typos, then clarity
Workflow
- Read the file
- Grep for
—to list formatting issues - Edit all issues in one pass per category
- Grep again for
—to confirm none remain - Report a summary of what was changed by category
Scope
- Works on any
.mdor.txtfile - If no file is specified, ask the user which file to fix
More from helderberto/skills
explain-code
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?" Don't use for modifying code, fixing bugs, or generating new implementations.
45ship
Commit and push changes using atomic commits. Use when user asks to "ship", "commit and push", or requests committing and pushing changes. Don't use for creating pull requests or reviewing changes before committing.
45safe-repo
Check for sensitive data in repository. Use when user asks to "check for sensitive data", "/safe-repo", or wants to verify no company/credential data is in the repository. Don't use for general code review, adding .gitignore entries, or scanning non-git directories.
41lint
Run linting and formatting checks. Use when user asks to "run linter", "/lint", "check linting", "fix lint errors", or requests code linting/formatting. Don't use for running tests, type-checking only, or projects without a lint script in package.json.
40tdd
Guides test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants test-first development, or requests TDD workflow. Don't use for writing tests after implementation, adding tests to existing untested code, or one-off test fixes.
40commit
Create git commits following repository style. Use when user asks to "create a commit", "commit changes", "/commit", or requests committing code to git. Don't use for pushing code, creating pull requests, or reviewing changes.
38