본문으로 건너뛰기
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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고