chaffjs 0.19.0 → 0.21.0

package/rules/sentence-initial-so.yaml

@@ -0,0 +1,63 @@
+id: sentence-initial-so
+layer: L2
+status: stable
+how_to_find: opener-pile
+word_list: so-opener
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 文頭の「So,」
+  en: Sentence opening with "So,"
+
+why:
+  ja: 英語で文の頭に置く「So,」は、話し言葉の間合いを書き言葉に持ち込んだものです。前の文との関係（理由・結果・話題の切り替え）を言わずに文をつなぎます。読点の無い「So far」「So that」は普通の書き出しなので数えません。
+  en: '"So," at the head of a sentence carries a spoken pause into writing. It joins the sentence to the last without saying how (a reason, a result, a change of topic). "So far" and "So that", without the comma, open a sentence on their own terms and are not counted.'
+
+message:
+  ja: 「{matched}」で始まる文が {count} 個あります（{limit} 個から）
+  en: '{count} {count|sentence opens|sentences open} with "{matched}" ({limit} needed)'
+
+how_to_fix:
+  ja: 「So,」を消して読み直してください。つながりが要るなら、それを言う語（Therefore、As a result）に替えます。
+  en: Delete "So," and reread. If the link is needed, use a word that says what it is ("Therefore", "As a result").
+
+levels: { strict: 1, normal: 1, relaxed: 3 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  literature: 'A narrator and a character speak as they speak: dialect ("would of"), "So," and hearsay are the voice.'
+  speech: "A transcript keeps the speaker's words: hedges and ら dropped as spoken."
+
+group: wording
+summary:
+  ja: 英語で、「So,」で始まる文（話し言葉の間合い）
+  en: A sentence that opens with "So,", a spoken pause carried into writing
+example:
+  en:
+    before: |
+      So, the release moves to Friday.
+    after: |
+      The release moves to Friday.
+
+not_flagged:
+  ja: 読点の付いた「So,」だけを見ます。「So far」「So that」「So the board decided」は数えません。英語の文書だけで動きます。小説と話し言葉では既定で止めています（話す調子がその文書の書き方のため）。
+  en: Only "So," with its comma. "So far", "So that" and "So the board decided" are not counted. Only in English documents; the fiction and speech presets turn it off, since a spoken tone is their form.
+level_meaning:
+  ja: 「So,」で始まる文が {limit} 個あれば指摘
+  en: reported once {limit} sentences open with "So,"
+rewrite:
+  depth: light
+  en:
+    direction: Delete the "So," at the head of the sentence. If the link to the last sentence is needed, use a word that says what it is.
+    pairs:
+      - before: So, we moved the release to Friday.
+        after: We moved the release to Friday.
+      - before: The vendor was late. So, the launch slipped.
+        after: The vendor was late. As a result, the launch slipped.
+    keep:
+      - the rest of the sentence
+    avoid:
+      - swapping "So," for another empty opener ("Well,", "Now,")

package/rules/sentence-rhythm.yaml

@@ -1,6 +1,6 @@
 id: sentence-rhythm
 # 「AI 生成は文の長さが揃う」は未検証の仮説。corpus 評価まで既定では動かさない。spec §26-4。
-status: experimental
+status: stable
 layer: L1
 how_to_find: sentence-rhythm
 severity: warning
@@ -27,7 +27,13 @@ levels:
   normal: 30
   relaxed: 20
 
-use_for: [blog, legal, docs, academic, literature, speech]
+use_for: [technical/readme, blog, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  academic: "Science writes in the passive, hedges its claims on purpose (may, suggest) and cites numbers as its evidence."
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  speech: "A speech opens with greetings and closes with thanks: that is its form, not padding."
 sources: [iwamoto-2026]
 
 group: readability
@@ -55,6 +61,7 @@ level_meaning:
   ja: 文の長さのばらつきが {limit}% 未満なら指摘
   en: reported when sentence length varies by less than {limit}%
 rewrite:
+  depth: light
   ja:
     direction: 長めの文のいくつかを、意味の切れ目で二つに割ってください。結論の文は短くします。言葉は足しません。
     pairs:

package/rules/sentence-spacing-consistency.yaml

@@ -0,0 +1,63 @@
+id: sentence-spacing-consistency
+layer: L1
+status: stable
+how_to_find: sentence-spacing
+languages: [en]
+severity: info
+
+name:
+  ja: 文と文のあいだの空白の数の混在
+  en: One and two spaces between sentences mixed
+
+why:
+  ja: 英語で、文と文のあいだを一つの空白で空ける所と二つで空ける所が混ざっていると、別々の所から貼り合わせた文書に見えます。どちらが正しいかは決めません。同じ行の中の文の切れ目だけを数え、文書の中で少ないほうを指します。
+  en: Sentences separated by one space in some places and two in others make a document look pasted together. chaff does not pick a side; it counts only breaks between sentences on one line and points at the less common way.
+
+message:
+  ja: 文のあいだに空白が {spaces} 個あります（この文書はふつう {usual} 個。{of} 箇所のうち {count} 箇所が違う）
+  en: "{spaces} {spaces|space|spaces} after this sentence, where the document usually leaves {usual} ({count} of {of})"
+
+# 少ないほうが 5 箇所以上で、全体の 2 割を超えるとき。書き損じではなく書き方が二通りあるので、1 件にまとめて両方の数を言う。
+messages:
+  mixed:
+    ja: "文のあいだを、空白二つで {spaced} 箇所、一つで {touching} 箇所空けています。この文書には空け方が二通りあります"
+    en: "Sentences are spaced two ways in this document ({spaced} with two spaces, {touching} with one)"
+
+how_to_fix:
+  ja: 文書の多いほうの数に合わせてください。
+  en: Match the spacing the rest of the document uses.
+
+levels: { strict: 1, normal: 1, relaxed: 3 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: consistency
+summary:
+  ja: 英語で、文と文のあいだの空白が一つの所と二つの所が混ざっている所
+  en: One space between sentences in some places and two in others
+example:
+  en:
+    before: |
+      We met. We talked. We agreed.  We left.
+    after: |
+      We met. We talked. We agreed. We left.
+
+not_flagged:
+  ja: ピリオド・疑問符・感嘆符で終わる文と、同じ行で続く次の文のあいだだけを見ます。行末の空白（Markdown の改行）は見ません。
+  en: Only the space after a sentence ending in a period, question or exclamation mark, before the next sentence on the same line. Spaces at the end of a line (a Markdown line break) are not counted.
+level_meaning:
+  ja: 少ないほうの空け方が {limit} 箇所あれば指摘
+  en: reported once the less common spacing appears {limit} times
+rewrite:
+  depth: light
+  en:
+    direction: Change the marked gap between sentences to the number of spaces the rest of the document uses.
+    pairs:
+      - before: We agreed.  We left.
+        after: We agreed. We left.
+      - before: The plan holds.  The date moves.
+        after: The plan holds. The date moves.
+    keep:
+      - every word and mark
+    avoid:
+      - changing spaces inside sentences

package/rules/shell-prompt-mix.yaml

@@ -0,0 +1,128 @@
+id: shell-prompt-mix
+layer: L1
+status: stable
+how_to_find: shell-prompt
+requires: [markdown]
+severity: info
+
+name:
+  ja: シェルのコマンドにプロンプトを付けたり付けなかったりしている
+  en: Shell commands with and without a prompt
+
+why:
+  ja: 「$ npm install」と「npm install」が一つの文書に混ざっていると、読み手は「$」まで打つのか迷い、コピーしたコマンドが動かないこともあります。シェルのブロック（```bash、```console）のうち、全部の行にプロンプト（$）を付けたブロックと、一つも付けないブロックを比べ、少ないほうを指します。出力と一緒に書いたブロック（プロンプトのある行と無い行が混ざる）は見ません。どちらに揃えるかは決めません。
+  en: 'When "$ npm install" and "npm install" both appear in one document, the reader wonders whether to type the "$", and a copied command may fail. chaff compares shell blocks (```bash, ```console) whose every line has a prompt ($) with those where no line has one, and points at the fewer. A block that shows a command with its output (some lines prompted, some not) is not read. Which way is right is not decided.'
+
+message:
+  ja: このブロックだけ、コマンドへのプロンプト（$）の付け方がほかと違います（ほかの {majority} ブロック）
+  en: This block writes its commands with a prompt ($) differently from the other {majority} blocks
+
+how_to_fix:
+  ja: 多いほうに揃えてください。コピーして使うコマンドなら、プロンプトを付けないほうが打ち間違えません。
+  en: Match the majority. For commands meant to be copied, leaving the prompt out avoids pasting it.
+
+levels: { strict: 3, normal: 2, relaxed: 1 }
+
+use_for: [technical, docs, blog, legal, academic, literature, speech]
+off_for:
+  legal: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  academic: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  literature: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  speech: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+
+group: consistency
+summary:
+  ja: シェルのブロックで、「$」のプロンプトを付けたコマンドと付けないコマンドが混ざっている所
+  en: Shell blocks that write commands with a "$" prompt in some places and without it in others
+example:
+  ja:
+    config: { genre: docs/manual }
+    before: |
+      # 使い方
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      $ npx chaffjs README.md
+      ```
+    after: |
+      # 使い方
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      npx chaffjs README.md
+      ```
+  en:
+    config: { genre: docs/manual }
+    before: |
+      # Usage
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      $ npx chaffjs README.md
+      ```
+    after: |
+      # Usage
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      npx chaffjs README.md
+      ```
+
+not_flagged:
+  ja: シェル以外の言語のブロック、言語名の無いブロック、コマンドと出力を一緒に書いたブロック、コメント（#）の行は見ません。少ないほうが {limit} ブロックを超えるときは使い分けとみなします。
+  en: Blocks in other languages or without a language, blocks that show a command with its output, and comment lines (#) are not read. When the fewer kind is more than {limit} blocks, it is taken as a choice.
+level_meaning:
+  ja: 少ないほうの書き方が {limit} ブロック以下のとき指摘
+  en: reported when the fewer style appears in {limit} blocks or fewer
+rewrite:
+  depth: light
+  ja:
+    direction: 指されたブロックのプロンプトを、文書の多いほうに揃えてください。付けない側に揃えるなら行の頭の「$ 」を消し、付ける側なら足します。コマンドそのものは変えません。
+    pairs:
+      - before: "$ npx chaffjs README.md"
+        after: "npx chaffjs README.md"
+      - before: "npm test"
+        after: "$ npm test"
+    keep:
+      - コマンドと引数
+    avoid:
+      - 出力の行にプロンプトを付ける
+  en:
+    direction: Bring the block's prompts in line with the document's majority. Toward no prompt, remove the "$ " at the start of each line; toward a prompt, add it. Leave the commands themselves unchanged.
+    pairs:
+      - before: "$ npx chaffjs README.md"
+        after: "npx chaffjs README.md"
+      - before: "npm test"
+        after: "$ npm test"
+    keep:
+      - the commands and their arguments
+    avoid:
+      - putting a prompt before an output line

package/rules/space-before-punctuation.yaml

@@ -1,6 +1,6 @@
 id: space-before-punctuation
 layer: L1
-status: experimental
+status: stable
 how_to_find: space-before-punctuation
 languages: [en]
 severity: warning

package/rules/spelling-consistency.yaml

@@ -1,6 +1,6 @@
 id: spelling-consistency
 layer: L3
-status: experimental
+status: stable
 how_to_find: spelling-variety
 word_list: spelling-variant
 extra_word_lists: [spelling-ize]
@@ -27,6 +27,8 @@ how_to_fix:
 levels: { strict: 49, normal: 34, relaxed: 20 }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "A narrator may hedge, speak with ら dropped, and spell as the work's time and place did."
 
 group: consistency
 summary:

package/rules/step-statement-mix.yaml

@@ -0,0 +1,76 @@
+id: step-statement-mix
+layer: L3
+status: stable
+how_to_find: step-statement
+languages: [en]
+requires: [pos]
+severity: info
+
+name:
+  ja: 手順の中に、指示でなく説明の文の手順がある
+  en: A step written as a statement among instructions
+
+why:
+  ja: 番号を振った手順は、読み手がそのとおりに手を動かす指示です。「Open the app.」「Run the installer.」の中に「The installer asks for a password.」のような説明の文が混ざると、読み手はそれも自分のすることかと迷います。英語の番号付きの箇条書きで、主語と動詞で始まる項目（The installer asks、You click）が、動詞で始まる指示の項目より少ないとき、少ないほうを指します。日本語の手順の文末（〜します／〜してください と それ以外）は no-mixed-desumasu と list-item-form-mix が見るので、この rule は英語だけです。
+  en: 'A numbered procedure is a list of things for the reader to do. When "The installer asks for a password." sits among "Open the app." and "Run the installer.", the reader wonders whether that is a step to take too. In an English numbered list, chaff points at the few items that open with a subject and a verb (The installer asks, You click) among items that open with the verb. Japanese step endings (〜します / 〜してください against the rest) are checked by no-mixed-desumasu and list-item-form-mix, so this rule is for English only.'
+
+message:
+  ja: この手順は、ほかの {count} 個の指示と違い、主語で始まる説明の文です
+  en: This step is a statement that opens with its subject, unlike the other {count} instructions
+
+how_to_fix:
+  ja: 読み手のすることを命令の形で書いてください。結果の説明なら、前の手順の後ろの文にするか、手順の外に出します。
+  en: Write what the reader does, as an instruction. If it describes a result, make it a second sentence of the step before, or move it out of the list.
+
+levels: { strict: 3, normal: 2, relaxed: 1 }
+
+use_for: [technical, docs, blog, legal, academic, literature, speech]
+off_for:
+  legal: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  academic: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  literature: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  speech: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+
+group: consistency
+summary:
+  ja: 英語の番号付きの手順で、命令の形の項目の中に、主語で始まる説明の項目が混ざっている所
+  en: A numbered procedure that mixes a statement (The installer asks) into instructions (Run the installer)
+example:
+  en:
+    config: { genre: docs/manual }
+    before: |
+      # Install
+
+      1. Open the terminal on your computer.
+      2. Run the installer from the downloads folder.
+      3. The installer asks for your password.
+      4. Restart the computer when it finishes.
+    after: |
+      # Install
+
+      1. Open the terminal on your computer.
+      2. Run the installer from the downloads folder.
+      3. Type your password when the installer asks for it.
+      4. Restart the computer when it finishes.
+
+not_flagged:
+  ja: "番号の無い箇条書き、三つに満たない手順、指示が半分に満たない番号付きの箇条書き（用語と説明の一覧など）、短い項目（「Setup」）、動詞の前に札や前置きのある項目（「Guests: …」「On the left bar, select …」）、主語で始まる項目が {limit} 個を超えるか指示より多い手順は見ません。項目の最初の行の最初の文だけを見ます。"
+  en: 'Bulleted lists, procedures of fewer than three steps, numbered lists where instructions are half or fewer (a list of terms, say), short items ("Setup"), items with a label or an opening phrase before the verb ("Guests: …", "On the left bar, select …"), and procedures where statements are more than {limit} or not fewer than the instructions are not reported. Only the first sentence on each item''s own line is read.'
+level_meaning:
+  ja: 説明の項目が {limit} 個以下で、指示の項目より少ないとき指摘
+  en: reported when {limit} or fewer steps are statements and they are fewer than the instructions
+rewrite:
+  depth: light
+  en:
+    direction: Turn the statement into an instruction for the reader, with the verb first, or fold it into the step before as a second sentence. Keep what the step says happens; do not add steps.
+    pairs:
+      - before: 3. The installer asks for your password.
+        after: 3. Type your password when the installer asks for it.
+      - before: 2. You click Save to keep the file.
+        after: 2. Click Save to keep the file.
+    keep:
+      - the order of the steps
+      - the names of buttons, files and commands
+    avoid:
+      - adding a step the text does not have
+      - merging two steps the reader does separately

package/rules/stock-transition.yaml

@@ -1,6 +1,6 @@
 id: stock-transition
 layer: L2
-status: experimental
+status: stable
 how_to_find: stock-transition
 word_list: stock-transition
 uses: [pos]
@@ -27,7 +27,13 @@ levels:
   ja: { strict: 2, normal: 3, relaxed: 5 }
   en: { strict: 4, normal: 6, relaxed: 10 }
 
-use_for: [blog, business, legal, docs, academic, literature, speech]
+use_for: [technical/readme, blog, business, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  academic: "Science writes in the passive, hedges its claims on purpose (may, suggest) and cites numbers as its evidence."
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  speech: "A speech opens with greetings and closes with thanks: that is its form, not padding."
 
 group: ai-tells
 summary:
@@ -54,6 +60,7 @@ level_meaning:
   ja: 決まった接ぎで始まる文が 1000 字あたり {limit} 個まで
   en: up to {limit} sentences per 1000 words opening with a stock transition
 rewrite:
+  depth: light
   ja:
     direction: 文頭の接ぎの語を消して読み返してください。繋がりが分からなくなる所だけ、前の文との関係（理由、例外、順番）を言葉で書きます。
     pairs:

package/rules/stray-space.yaml

@@ -1,11 +1,11 @@
 id: stray-space
 layer: L3
-status: experimental
+status: stable
 how_to_find: stray-space
 # どの境目が一続きの語句の中かは、語の品詞で決める。品詞が無ければ動かない。
 requires: [pos]
 languages: [ja]
-severity: warning
+severity: info
 
 name:
   ja: 語句の途中に空白がある

package/rules/summary-fact-mismatch.yaml

@@ -0,0 +1,125 @@
+id: summary-fact-mismatch
+layer: L3
+status: stable
+how_to_find: summary-fact-mismatch
+requires: [quantities]
+uses: [pos]
+severity: warning
+
+name:
+  ja: 冒頭や要約の値が本文と違う
+  en: A summary value that differs from the body
+
+why:
+  ja: 冒頭や「概要」の節は、本文を読まない人も読みます。そこに書いた値が本文と違うと、要約だけを読んだ人が間違った値を持ち帰ります。本文を直したあとに、要約を直し忘れると起きます。最初の見出しより前の文と、概要・要約・まとめの節の「項目：値」「項目は値です」を、本文の同じ項目の値と比べます。本文の値が一通りに揃っていて、要約の値がそれと違うときだけ指します。
+  en: 'The opening and the summary are read by people who never read the body. A value there that differs from the body sends them away with the wrong one. It happens when the body is corrected and the summary is not. Values written as "Item: value" or "The item is value" before the first heading, or in a section headed Summary, Abstract or Overview, are compared with the body''s values for the same item; it is pointed out only when the body gives one value throughout and the summary gives another.'
+
+message:
+  ja: 冒頭・要約の「{label}」 {value} が、本文の {other} と違います
+  en: 'The summary gives "{label}" as {value}, but the body gives {other}'
+
+how_to_fix:
+  ja: 本文と要約のどちらが正しいかを確かめて、もう一方を直してください。
+  en: Check which is right, the summary or the body, and correct the other.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 冒頭や概要の節に書いた値（締切、料金など）が、本文の同じ項目の値と違う所
+  en: A value in the opening or the summary (a deadline, a fee) that differs from the same item in the body
+example:
+  ja:
+    before: |
+      # 説明会
+
+      参加費は3,000円です。
+
+      ## 申し込み
+
+      参加費は3,500円です。
+    after: |
+      # 説明会
+
+      参加費は3,500円です。
+
+      ## 申し込み
+
+      参加費は3,500円です。
+  en:
+    before: |
+      # Workshop
+
+      The fee is $300.
+
+      ## Registration
+
+      The fee is $350.
+    after: |
+      # Workshop
+
+      The fee is $350.
+
+      ## Registration
+
+      The fee is $350.
+
+not_flagged:
+  ja: 本文に同じ項目の値が二通り以上あるとき（回ごと、対象ごとの値）は、要約がどれと合うべきか決まらないので言いません。単位の違う値、条件の付いた値（「3,000円から」）も比べません。
+  en: When the body gives the item more than one value (per session, per group), which one the summary should match is not settled, so nothing is said. Values in different units and values with a condition ("from $300") are not compared.
+rewrite:
+  depth: light
+  ja:
+    direction: 要約と本文のどちらの値が正しいかを書き手に確かめ、もう一方を直してください。要約の値を本文から写すときは、単位と条件も一緒に写します。
+    pairs:
+      - before: |
+          概要：締切は10月5日です。
+          （本文）締切は10月7日です。
+        after: |
+          概要：締切は10月7日です。
+          （本文）締切は10月7日です。
+      - before: |
+          ## 概要
+          定員：30名
+          ## 詳細
+          定員：40名
+        after: |
+          ## 概要
+          定員：40名
+          ## 詳細
+          定員：40名
+    keep:
+      - 本文で確かめた値
+      - 要約の短さ
+    avoid:
+      - どちらが正しいかを推測で決める
+      - 要約から値を消して、ぼかした言い方にする
+  en:
+    direction: Ask the writer whether the summary or the body is right, and correct the other. When copying a value into the summary, copy its unit and condition too.
+    pairs:
+      - before: |
+          Summary: the deadline is May 3.
+          (body) The deadline is May 5.
+        after: |
+          Summary: the deadline is May 5.
+          (body) The deadline is May 5.
+      - before: |
+          ## Overview
+          Seats: 30
+          ## Details
+          Seats: 40
+        after: |
+          ## Overview
+          Seats: 40
+          ## Details
+          Seats: 40
+    keep:
+      - the value confirmed in the body
+      - the summary's brevity
+    avoid:
+      - guessing which value is right
+      - removing the value from the summary and writing something vaguer

package/rules/table-header-variant.yaml

@@ -0,0 +1,113 @@
+id: table-header-variant
+layer: L2
+status: stable
+how_to_find: table-header-variant
+requires: [markdown]
+severity: info
+
+name:
+  ja: 表の見出しの書き方が表ごとに違う
+  en: One table header written two ways
+
+why:
+  ja: 同じ欄を、ある表では「担当者」、別の表では「担当」と書くと、読み手は別の欄かと迷い、表を見比べるときに手が止まります。chaff は表の見出しの行と、二列の表の左の欄（項目名）を集め、幅・大文字小文字・空白・ハイフン・中黒をそろえたうえで、名前を変えない字（者・欄・名・等）を外すと同じになる見出しを、同じ欄の書き方と見ます。そのうえで、文書の中で少ないほうの書き方を指摘します。どちらが正しいかは決めません。
+  en: When one table says "Owner" and another says "Owners" for the same column, the reader wonders whether they are different columns and stops to compare. chaff collects the header row of every table and the left cell of every two-column table (a field name). It treats two headers as one label when they are the same after folding width, case, spaces, hyphens and middle dots and dropping an ending that leaves the meaning alone (s, es). It then points at the less common spelling in the document, without deciding which is right.
+
+message:
+  ja: 表の見出しを「{written}」と書いています（この文書のほかの表は「{usual}」。{of} 箇所のうち {count} 箇所が違う）
+  en: 'The table header "{written}" here, where the document''s other tables write "{usual}" ({count} of {of})'
+
+how_to_fix:
+  ja: 同じ欄なら、文書の多いほうの書き方にそろえてください。本当に別の欄なら、違いが分かる名前にします。
+  en: If it is the same column, write it the way the rest of the document does. If it really is a different column, give it a name that shows the difference.
+
+# 少ないほうの書き方が、その見出しの何パーセントまでなら「混ざっている」と見るか。1 対 1 も指摘する。
+levels: { strict: 50, normal: 50, relaxed: 34 }
+
+use_for: [blog, business, technical, docs, academic, legal, literature, speech]
+
+group: consistency
+summary:
+  ja: 同じ欄の見出しを、表によって「担当者」と「担当」のように書き分けている所
+  en: The same column header written two ways across a document's tables, such as Owner and Owners
+
+example:
+  ja:
+    config: { genre: business/report }
+    before: |
+      | 作業 | 担当者 |
+      | --- | --- |
+      | 発注 | 山田 |
+
+      | 作業 | 担当 |
+      | --- | --- |
+      | 検品 | 鈴木 |
+    after: |
+      | 作業 | 担当者 |
+      | --- | --- |
+      | 発注 | 山田 |
+
+      | 作業 | 担当者 |
+      | --- | --- |
+      | 検品 | 鈴木 |
+  en:
+    config: { genre: business/report }
+    before: |
+      | Task | Owner |
+      | --- | --- |
+      | Order | Kim |
+
+      | Task | Owners |
+      | --- | --- |
+      | Check | Lee |
+    after: |
+      | Task | Owner |
+      | --- | --- |
+      | Order | Kim |
+
+      | Task | Owner |
+      | --- | --- |
+      | Check | Lee |
+
+not_flagged:
+  ja: 文字の無い見出し（数や記号だけ）、コードの例の中の表、見出しの違いが名前を変える場合（「日付」と「日時」）は見ません。二列の表でなければ、左の欄は見出しとして集めません。
+  en: Headers without letters (numbers or symbols only), tables inside a code sample, and headers that differ in meaning (Date and Time) are not compared. The left cell is collected only in two-column tables.
+level_meaning:
+  ja: 少ないほうの書き方が、その見出しの {limit}% 以下のとき指摘
+  en: reported when the less common spelling is {limit}% of the header's uses or less
+rewrite:
+  depth: light
+  ja:
+    direction: 同じ欄の見出しを、文書の中で多いほうの書き方にそろえてください。表の中身と並びは変えません。
+    pairs:
+      - before: |
+          | 作業 | 担当 |
+        after: |
+          | 作業 | 担当者 |
+      - before: |
+          | 備考欄 | 金額 |
+        after: |
+          | 備考 | 金額 |
+    keep:
+      - 表の行と列の並び
+      - 升の中身
+    avoid:
+      - 別の欄を同じ名前にする
+      - 多いほうの書き方を少ないほうに合わせる
+  en:
+    direction: Rename the odd header to the spelling the document's other tables use for that column. Keep the cells and their order.
+    pairs:
+      - before: |
+          | Task | Owners |
+        after: |
+          | Task | Owner |
+      - before: |
+          | E-mail | Phone |
+        after: |
+          | Email | Phone |
+    keep:
+      - the rows and columns of every table
+      - the content of every cell
+    avoid:
+      - giving two different columns the same name
+      - changing the common spelling to match the odd one