prose-check
Checks documentation prose for spelling and grammar problems and reports each with file, line, and a suggestion. Use when the user asks to "check the writing", "proofread the docs", or "lint the prose".
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- prose-check
- description
- Checks documentation prose for spelling and grammar problems and reports each with file, line, and a suggestion. Use when the user asks to "check the writing", "proofread the docs", or "lint the prose".
03 SKILL.md 正文
prose-check
Report spelling and grammar problems in Markdown files.
Steps
- Find every
*.mdfile outsidenode_modules/and.git/. - Run
vale --output=JSON .(vale must already be on PATH; if it is not, stop and say so). - Map each result to
{file, line, kind, text, suggest}.
Output
{"problems": [{"file": "docs/intro.md", "line": 9, "kind": "grammar", "text": "less files", "suggest": "fewer files"}]}
Return {"problems": []} when vale reports nothing.
04 同仓库更多 Skills
toy-check
A skill that checks things in the repository and reports what it finds.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
zirkel-verify-assumptions
Checks exactly ONE named assumption against real evidence in at most 3 steps and reports one outcome: confidence raised (>=90), reading changed, or still unresolved. Use to resolve a single load-bearing uncertainty — typically a blocking entry surfaced by zirkel-clarify-scope: "verify this one assumption", "is it actually true that X", "check this before we rely on it". For multiple uncertainties, invoke once per uncertainty — the step budget is never shared.