Editor copy
Copy-edit written content: fix grammar, style, and phrasing errors directly in the file. Use when the user asks to proofread, copy-edit, or clean up an article, blog post, doc, README, email, or any prose. Also use when they say "fix the grammar", "tighten this up", or "do a copy pass". Do NOT use for: structural or engagement review (use the editor-content skill), or agent instruction files (AGENTS.md, SKILL.md, CLAUDE.md).From its SKILL.md
npx -y skills add imankulov/skills --skill editor-copyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, as published. Nobody here has run it
Editor: copy edit
Copy-edit the file as an expert editor.
The file(s) to copy-edit: $ARGUMENTS
If no file is given, or not immediately obvious from previous discussion or context, ask which file or text to edit.
Scope: what to edit
If the file is tracked in git, assume the committed version (HEAD) is already clean.
Run git diff HEAD -- <file> and copy-edit only the changed hunks, reading just
enough surrounding lines to understand tone and to make Edit matches unique. Do not
re-edit unchanged text.
Do a full pass instead when any of these hold:
- the file is untracked or not in a git repository;
- the diff against HEAD is empty (the user invoked the skill on a committed file, so they want the whole thing checked);
- the user asks for a full pass or says the committed version was never edited.
If the file (or the relevant hunks) is already in context and unchanged since, work from context instead of re-reading.
Process
- Invoke the
writingskill via the Skill tool to load the prose guidelines. - Determine the scope (changed hunks or full file) and read what it requires.
- Edit each issue in-place with the Edit tool.
- After all edits, give a brief summary of the changes.
Constraints
- Fix glaring grammar and style errors, not stylistic preferences.
- Prefer phrasings closest to the original.
- Limit edits to grammar and phrasing, without rewriting content, adding information, or touching code blocks.
- Flag unclear meaning as a question rather than guessing.
- If the writing is already good, say so.