← ClaudeAtlas

prose-gatelisted

Use when writing or finishing any comment, docstring, README, design document, implementation plan, GitHub issue, PR body, or commit message, and before reporting that writing work is done. Use it when a task changed prose as a byproduct of changing code, and when a review finding asks for a wording change.
rgant/claude-plugins · ★ 0 · Data & Documents · score 72
Install: claude install-skill rgant/claude-plugins
# Prose Gate ## Overview The rules are not the problem. Agents that read the standard write to it. The failure is that nobody runs a check, so prose ships unread. **Prose is not done until `check_prose.py` reports it clean.** Run the gate. Do not judge your own sentences by eye. **REQUIRED SUB-SKILL:** `writing:simple-english` holds the 53 STE rules. Load it to fix a finding in a procedure. To fix a finding in an explanation, read `${CLAUDE_PLUGIN_ROOT}/guides/explanations.md`. For a commit message, a PR title, or a PR description, load `writing:commit-message` instead. ## The gate Run this before you report any task that wrote or changed prose: ```sh uv run --no-project --quiet --python ">=3.14" "${CLAUDE_SKILL_DIR}/check_prose.py" ``` It reads only the lines the branch adds or changes, against the merge-base with the default branch. Staged, unstaged, and untracked files are all in scope. - A plan or a draft has no branch diff yet. Use `--files <path>` or pipe the draft to `--stdin`. - A review body, a PR comment, or a chat message is a message between people. Add `--message`. It allows contractions and the progressive. Docs, comments, and PR descriptions never take it. - An agent instruction file never appears. `CLAUDE.md`, `AGENTS.md` and `GEMINI.md` address a model, not a person, and the style rules they carry are the ones inside them. To check one anyway, name it with `--files`. - A generated file never appears either. `CHANGELOG.md` holds commit subje