note-writer
Review English text edits in org-mode files from a git diff. Checks grammar, style, translation quality (RU→EN), and produces a clean patch. Use when reviewing org-mode writing, checking English quality of documentation edits, or auditing translation naturalness.
- License 许可
- GPL-3.0
- 所属仓库
- Artawower/kaizen
- 最近更新
- 2026-11-10
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- note-writer
- description
- Review English text edits in org-mode files from a git diff. Checks grammar, style, translation quality (RU→EN), and produces a clean patch. Use when reviewing org-mode writing, checking English quality of documentation edits, or auditing translation naturalness.
03 SKILL.md 正文
EN Writing & Translation QA (org-mode, git diff)
VERSION: 1.1
Goal
Review English text edits provided as a unified git diff (source text is org-mode) and help the user:
- fix grammar errors
- improve style and clarity
- assess translation quality (RU→EN influence)
- explain each issue with a short rule-based note
- propose better rewrites while preserving meaning and org-mode markup
Input
- git_diff (required): unified diff of an org-mode file — provide inline or ask the user to paste it
- optional context: audience, tone, register; English variant (American/British); strictness (low/medium/high)
Scope
- Review ONLY added/modified lines from the diff.
- Use removed lines only for context.
- Do not rewrite the whole document.
- If a change creates a consistency problem with unchanged nearby text, mention briefly.
Process
-
Parse the diff — identify hunks, classify lines (
+added,-removed,context). Pair removed/added blocks when it is clearly a modification. -
Grammar & correctness pass — for each changed line detect mistakes (articles, prepositions, tense, agreement, punctuation, sentence boundaries, word order). Provide: Problem → Fix → Explanation.
-
Style & clarity pass — improve naturalness and flow with minimal edits. Prefer concise, idiomatic English. Preserve tone/voice unless it harms clarity.
-
Translation quality check — detect Russianisms and literal translation patterns: unnatural collocations, incorrect prepositions/articles, calques/false friends, overly heavy nominalizations, passive voice where unnatural, word order mirroring Russian. Give 1–2 plausible meanings when ambiguous, offer safe rewrites.
-
Rule snippet for every flagged issue — Rule name + 1–2 sentence explanation + tiny example if helpful.
-
Produce final rewrite — "Suggested patch (clean)" section with revised lines only, no diff markers, org-mode markup preserved.
Priority levels
- High: grammar error, meaning distortion, clearly non-native/incorrect collocation, broken org syntax
- Medium: awkward but understandable, wordiness, minor punctuation
- Low: optional polish, alternative phrasing
Output format
- Overall assessment — Grammar / Style/flow / Translation naturalness
- Issues list (prioritized High → Medium → Low), each with: Problem → Fix, Why, Rule snippet
- Suggested patch (clean) — revised lines, no diff symbols, org-mode markup intact
- Optional: 3 learning takeaways (recurring patterns)
Constraints
- Respond in the user's language for meta-commentary; keep proposed English rewrites in English.
- Ask max 2 clarification questions, only if meaning is genuinely unclear.
- Do not introduce new facts or content.
- Do not remove org-mode markup unless broken; explain any markup changes.
04 同仓库更多 Skills
yt-analyze
Fetch YouTrack task + comments via MCP, critically analyze relevance and requirements, produce concise summary of what to implement, and build an implementation plan mapped to codebase. Trigger - YouTrack issue ID or request to "analyze task", "plan task", "break down YT issue".
youtrack-task
Analyzes a YouTrack issue, reviews comments and attachments, and proposes or creates actionable subtasks. Use when the user gives a YouTrack issue ID and wants synthesis, decomposition, or follow-up tasks.
youtrack-search
Searches YouTrack from natural language or native query syntax and returns a concise report with the most relevant issues. Use when the user wants to find issues, triage work, or translate a plain-language query into YouTrack search.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
vitest
Plan and write Vitest tests for changed code. Analyses git diff, checks existing tests, produces a concrete test plan using flat test structure (no describe/it blocks). Use when adding tests for new/changed code, improving Vitest coverage, or asking what to test after a change.