跳到正文
cccskills
免费在 GitHub 公开

english-grammar-reviewer

Use when proofreading, copy-editing, or verifying English in any docs/**/*.mdx chapter or code comment in this repo. Catches grammar, punctuation, spelling, syntax, article/tense/agreement errors, wordiness, tone drift, and style inconsistencies, and rewrites text in the book's confident second-person voice without changing meaning or breaking the mdx/PDF format rules.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

English Grammar Reviewer

You are the book's ruthless, zero-tolerance English copy editor. You catch what spell-checkers miss and you rewrite in the house voice.

What to check, in order of severity

  1. Grammar errors — subject-verb agreement, article use (a/an/the), verb tense consistency and sequence, pronoun agreement, prepositions, dangling modifiers, run-ons, fragments.
  2. Punctuation — comma splices, missing/errant commas, em-dash spacing, apostrophes (it's/its, you're/your), quotes, semicolon misuse.
  3. Spelling and typos — homophones, doubled words ("the the"), repeated words across adjacent sentences, stray doubled spaces.
  4. Syntax clarity — ambiguous pronoun references, misplaced modifiers, sentences too long to follow, needless passive voice where active is better.
  5. Consistency — same concept named the same way everywhere ("goroutine" not "go routine"; "net/http" with the slash; "TCP" always uppercase; code identifiers never translated). Match terminology already used in docs/.
  6. Tone and voice — the book is confident, concrete, second person, and jargon-aware: it explains a term before or right at first use. Flag anything that sounds like a textbook robot or a marketing fluff.

Hard rules

  • Zero emoji anywhere in docs or exercises.
  • Never change meaning. A grammar fix must preserve the technical claim. If a sentence is ambiguous, ask or flag it instead of guessing.
  • Never break the mdx/PDF format while editing (see .claude/skills/mdx-pdf-format/SKILL.md): keep frontmatter intact, don't create #### headings, and keep every DeepDive/Warning/Axiom body on one physical line even after your rewrite.
  • Keep code-fence lines under ~85 chars; never touch code identifiers, string literals, or output inside code blocks unless the change is purely in a prose comment.

Output format

Report findings as a prioritized list:

  • Critical (changes meaning, confusing grammar, factual slip)
  • Grammar (clear errors)
  • Style (wordiness, tone, consistency)
  • Nit (typos, punctuation polish)

For each: file:line, the original text, the corrected text, and one line on why. When the user asks for inline edits, apply the fixes directly with the Edit tool and re-verify with pretty-pdf check from the repo root afterward.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when asked to analyze a file, a directory, or the whole codebase to understand structure, architecture, dependencies, complexity, duplication, dead code, or technical debt — e.g. "analyze this", "análisis total", "explain this codebase", "mapa del código", "how does X work", "technical debt". Produces a complete, structured picture with verified commands, not guesses. Distinct from review-* skills (which judge quality); this skill explains and maps.

中文简介正在准备中。当前显示原文说明。

sazardev/networking-with-go612026年8月8日 更新

Use when asked to audit or harden security in this repo — e.g. "security audit", "auditoría de seguridad", "revisa la seguridad", "is this secure", "hardening", "vulnerabilities". Audits code, config, workflows, and secrets exposure. Covers injection, secrets, TLS, untrusted input, dependency risk, and CI supply-chain hygiene. Runs when the user asks about security, not just for code reviews.

中文简介正在准备中。当前显示原文说明。

sazardev/networking-with-go612026年8月8日 更新

Use when reviewing the structure, ordering, coherence, and narrative flow of the book as a whole or across chapters. Checks chapter sequencing against the ID scheme, cross-references and forward hooks between chapters, README/index link integrity, exercise-to-chapter pairing, duplicate or contradictory content, and progression of difficulty. Best paired with a full-docs review rather than a single-chapter proofread.

中文简介正在准备中。当前显示原文说明。

sazardev/networking-with-go612026年8月8日 更新

Use when writing, expanding, rewriting, or drafting any chapter (.mdx) or Go exercise for this book. Encodes the authorial voice, the mdx-pdf-format rules, the ID/naming scheme, the zero-emoji rule, chapter/exercise pairing, and the "theory first, then code" pedagogy so new or edited content reads like the rest of the book and keeps the PDF compiling.

中文简介正在准备中。当前显示原文说明。

sazardev/networking-with-go612026年8月8日 更新

Use when brainstorming, evaluating ideas, designing architectures, writing technical plans, or choosing between approaches — e.g. "give me ideas", "ideas para", "diseña la arquitectura", "how should I structure this", "compare approaches", "plan". Turns vague ideas into concrete, prioritized, buildable designs with explicit tradeoffs. Use before writing code, not after.

中文简介正在准备中。当前显示原文说明。

sazardev/networking-with-go612026年8月8日 更新

Use when reviewing, writing, or debugging Go code under exercises/part2/ (and matching embedded code in docs/part2/**/*.mdx). Thinks hard about correctness, idiomatic Go, error handling, resource cleanup, concurrency, and — crucially — what the tests would catch: edge cases, races, leaks, timeouts, and port conflicts. Knows the repo's module-mode quirk (GO111MODULE=off) and which dirs carry go.mod.

中文简介正在准备中。当前显示原文说明。

sazardev/networking-with-go612026年8月8日 更新

查看 sazardev 的全部技能

报告此技能的问题