chaffjs 0.21.0 → 0.22.0

package/rules/toc-heading-mismatch.yaml

@@ -0,0 +1,136 @@
+id: toc-heading-mismatch
+layer: L3
+status: stable
+how_to_find: toc-heading
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 見出しの無い目次の項目
+  en: A table-of-contents entry with no heading
+
+why:
+  ja: 目次に「3.2 費用」とあるのに本文にその見出しが無ければ、読み手は目次から探しても行き着けません。見出しを書き換えたり節を消したりしたあとに、目次だけが古いまま残ると起きます。目次の項目と見出しの言葉を突き合わせれば、機械で言えます。
+  en: When the table of contents lists "3.2 Costs" and the text has no such heading, the reader cannot get there from the contents. It happens when a heading is renamed or a section removed and the contents are left as they were. Matching the entries against the headings is mechanical.
+
+message:
+  ja: 目次の「{entry}」に合う見出しがありません
+  en: 'No heading matches the contents entry "{entry}"'
+
+how_to_fix:
+  ja: 目次を見出しに合わせて直すか、消えた節の項目を目次から消してください。
+  en: Update the entry to match the heading, or remove the entry for a section that is gone.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 目次（「目次」「Contents」の見出しの下の箇条書き）の項目のうち、文書のどの見出しとも合わないもの
+  en: An entry of the table of contents (the list under a "Contents" heading) that matches no heading of the document
+example:
+  ja:
+    before: |
+      ## 目次
+
+      - 1 概要
+      - 2 費用
+      - 3 日程
+
+      ## 1 概要
+
+      本書の概要です。
+
+      ## 2 料金
+
+      料金の説明です。
+
+      ## 3 日程
+
+      日程の説明です。
+    after: |
+      ## 目次
+
+      - 1 概要
+      - 2 料金
+      - 3 日程
+
+      ## 1 概要
+
+      本書の概要です。
+
+      ## 2 料金
+
+      料金の説明です。
+
+      ## 3 日程
+
+      日程の説明です。
+  en:
+    before: |
+      ## Contents
+
+      - 1 Overview
+      - 2 Costs
+      - 3 Schedule
+
+      ## 1 Overview
+
+      An overview.
+
+      ## 2 Fees
+
+      The fees.
+
+      ## 3 Schedule
+
+      The schedule.
+    after: |
+      ## Contents
+
+      - 1 Overview
+      - 2 Fees
+      - 3 Schedule
+
+      ## 1 Overview
+
+      An overview.
+
+      ## 2 Fees
+
+      The fees.
+
+      ## 3 Schedule
+
+      The schedule.
+
+not_flagged:
+  ja: 項目と見出しは、空白・記号・大文字小文字を無視して比べ、頭の番号（1.2、2-1）と、ページ番号（…… 12）を外しても比べます。リンクの項目は字の部分を比べます（リンクの行き先は broken-link が見ます）。目次の項目の半分より多くが見出しに合わない文書は、本文と別の章立ての目次と読んで言いません。Markdown の見出しのある文書だけを見ます。
+  en: Entries and headings are compared ignoring spaces, punctuation and case, and again without a leading number (1.2, 2-1) or a page number (.... 12). For a linked entry the link text is compared (broken-link checks where it points). When more than half of the entries match no heading, the contents are read as following another outline and nothing is reported. Only Markdown documents with headings are checked.
+
+rewrite:
+  ja:
+    direction: 目次の項目を、本文の見出しの言葉と番号に合わせてください。節を消したのなら、その項目を目次から消します。
+    pairs:
+      - before: 目次の「2 費用」（見出しは「2 料金」）
+        after: 目次の「2 料金」
+      - before: 目次の「4 付録」（本文に付録の節が無い）
+        after: 目次から「4 付録」を消す
+    keep:
+      - 本文の見出し
+      - 目次の並び順
+    avoid:
+      - 目次に合わせて本文の見出しを書き換える
+  en:
+    direction: Make each contents entry match the heading's words and number. If a section was removed, remove its entry.
+    pairs:
+      - before: The contents entry "2 Costs" (the heading is "2 Fees")
+        after: The contents entry "2 Fees"
+      - before: The contents entry "4 Appendix" (no appendix in the text)
+        after: The entry "4 Appendix" removed
+    keep:
+      - the headings in the text
+      - the order of the contents
+    avoid:
+      - renaming a heading in the text to match the contents

package/rules/unclosed-code-fence.yaml

@@ -0,0 +1,107 @@
+id: unclosed-code-fence
+layer: L1
+status: stable
+how_to_find: unclosed-code-fence
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 閉じていないコードブロック
+  en: Unclosed code fence
+
+why:
+  ja: 「```」で始めたコードブロックを閉じ忘れると、Markdown は文書の終わり（リストの項目の中ならその項目の終わり）までをすべてコードとして表示します。後ろの見出しも本文も等幅の字の塊になり、読み手には文書が壊れて見えます。
+  en: A code block opened with "```" and never closed runs to the end of the document (or of the list item it is in), so Markdown shows everything after it as code. The headings and text that follow turn into one block of monospaced text, and the document looks broken.
+
+message:
+  ja: 「{fence}」で始めたコードブロックが閉じていません
+  en: 'The code block opened with "{fence}" is never closed'
+
+how_to_fix:
+  ja: コードの終わりに、始めと同じ記号を同じ数以上並べた行（「```」）を足してください。
+  en: Add a line after the code with the same character, at least as many ("```").
+
+placeholders:
+  fence:
+    ja: 記号
+    en: the fence
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 「```」で始めたまま閉じていないコードブロック（後ろがすべてコードになる）
+  en: A code block opened with "```" and never closed (everything after it shows as code)
+example:
+  ja:
+    before: |
+      手順は次のとおりです。
+
+      ```sh
+      npm install
+
+      ## 確認
+
+      動くことを確かめます。
+    after: |
+      手順は次のとおりです。
+
+      ```sh
+      npm install
+      ```
+
+      ## 確認
+
+      動くことを確かめます。
+  en:
+    before: |
+      Install it first.
+
+      ```sh
+      npm install
+
+      ## Check
+
+      Make sure it runs.
+    after: |
+      Install it first.
+
+      ```sh
+      npm install
+      ```
+
+      ## Check
+
+      Make sure it runs.
+
+not_flagged:
+  ja: 閉じたコードブロック、字下げで書いたコードブロック、引用の中のコードブロックは指しません。
+  en: A closed code block, an indented code block, and a code block in a quotation are not reported.
+rewrite:
+  depth: light
+  ja:
+    direction: コードの終わりに閉じる行（「```」）を足してください。どこまでがコードかは、コマンドや出力の並びの終わりで決めます。コードの中身は変えません。
+    pairs:
+      - before: 「```sh」「npm install」「## 確認」
+        after: 「```sh」「npm install」「```」「## 確認」
+      - before: 「~~~」「SELECT 1;」のまま文書が終わる
+        after: 「~~~」「SELECT 1;」「~~~」
+    keep:
+      - コードの中身
+      - 始めの行の言語名
+    avoid:
+      - 後ろの本文までコードの中に入れる
+  en:
+    direction: Add a closing line ("```") where the code ends; the code ends where the commands or the output stop. Keep the code as it is.
+    pairs:
+      - before: '"```sh", "npm install", "## Check"'
+        after: '"```sh", "npm install", "```", "## Check"'
+      - before: 'the document ends after "~~~" and "SELECT 1;"'
+        after: '"~~~", "SELECT 1;", "~~~"'
+    keep:
+      - the code
+      - the language name on the opening line
+    avoid:
+      - putting the text after it inside the code block

package/rules/uncomparable-graded.yaml

@@ -0,0 +1,65 @@
+id: uncomparable-graded
+layer: L2
+status: stable
+how_to_find: phrase-match
+word_list: uncomparable-graded
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 比べられない形容詞に付けた程度
+  en: An uncomparable adjective given a degree
+
+why:
+  ja: 英語の「unique」「unanimous」「impossible」は、そうであるかないかの二つしかない状態を言います。「very unique」「more unanimous」と程度を付けても何も足されず、読み手は書き手が語の意味を確かめていないと受け取ります。語の一覧は言語ごとの語彙表にあります。
+  en: '"Unique", "unanimous" and "impossible" name a state that holds or does not. "Very unique" or "more unanimous" adds nothing, and tells the reader the writer did not weigh the word. The phrases are listed in the lexicon.'
+
+message:
+  ja: 「{matched}」は、程度の無い形容詞に程度を付けています
+  en: '"{matched}" grades an adjective that has no degrees'
+
+how_to_fix:
+  ja: 程度の語を外すか、本当に言いたい程度の言える語に替えてください（very unique → unique、または unusual）。
+  en: Drop the grade, or use a word that has degrees ("very unique" → "unique", or "unusual").
+
+levels: { strict: 1, normal: 1, relaxed: 2 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: 'A narrator or a character may say "very unique"; the voice is the author''s choice.'
+
+group: wording
+summary:
+  ja: 英語で、「very unique」「more unanimous」のように、程度の無い形容詞に付けた程度
+  en: A degree given to an adjective that has none, such as "very unique" or "more unanimous"
+example:
+  en:
+    before: |
+      The design is very unique.
+    after: |
+      The design is unusual.
+
+not_flagged:
+  ja: 一覧にある組み合わせだけを見ます。「almost」「nearly」のように近さを言う語（almost unique、nearly impossible）は指しません。英語の文書だけで動き、文学のジャンルは対象にしません。
+  en: Only the pairs on chaff's list are checked. Words that say how close ("almost unique", "nearly impossible") are not reported. English documents only; literature is not checked.
+level_meaning:
+  ja: 当てはまる言い回しが {limit} 箇所あれば指摘
+  en: reported once there are {limit}
+sources: [proselint]
+rewrite:
+  depth: light
+  en:
+    direction: Drop the grade before the adjective, or swap the adjective for one that has degrees when a degree is meant. Change nothing else in the sentence.
+    pairs:
+      - before: The design is very unique.
+        after: The design is unusual.
+      - before: The vote was more unanimous than last year.
+        after: The vote was unanimous this year.
+      - before: A fix before Friday is extremely impossible.
+        after: A fix before Friday is impossible.
+    keep:
+      - the claim the sentence makes
+      - the rest of the sentence
+    avoid:
+      - adding a new grade ("truly unique") in place of the old one

package/rules/unrendered-emphasis.yaml

@@ -0,0 +1,73 @@
+id: unrendered-emphasis
+layer: L1
+status: stable
+how_to_find: unrendered-emphasis
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 太字にならずに見える「**」
+  en: Unrendered emphasis marks
+
+why:
+  ja: 「**」や「__」は、Markdown が対にできたときだけ太字になり、対にできなければそのまま記号として表示されます。閉じ忘れ（「**重要」）のほか、日本語では「**「重要」**です」のように括弧や句読点の内側に記号を置き、外側に字が続くと、CommonMark の決まりで閉じられず、読み手には「**」が見えます。
+  en: '"**" and "__" turn into bold only when Markdown can pair them; otherwise they show as written. Besides one left open ("**important"), a mark with punctuation inside and a letter outside (Japanese "**「重要」**です") cannot close under CommonMark''s rules, and the reader sees the "**".'
+
+message:
+  ja: 「{mark}」が太字にならず、そのまま表示されます
+  en: '"{mark}" is not turned into bold and shows as written'
+
+how_to_fix:
+  ja: 閉じ忘れなら閉じる「**」を足してください。括弧や句読点の内側に置いた記号は、括弧の外に出すか（「**「重要」**」の外側に空白を置く）、括弧ごと太字にしないでください。
+  en: If it was left open, add the closing "**". If punctuation sits inside the mark, move the mark outside the punctuation, or put a space outside it.
+
+placeholders:
+  mark:
+    ja: 記号
+    en: the mark
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 対にならず、太字にならないまま記号として見える「**」「__」
+  en: '"**" or "__" that Markdown cannot pair and shows as written'
+example:
+  ja:
+    before: 締め切りは**金曜日です。遅れないようにしてください。
+    after: 締め切りは**金曜日**です。遅れないようにしてください。
+  en:
+    before: The deadline is **Friday. Do not be late.
+    after: The deadline is **Friday**. Do not be late.
+
+not_flagged:
+  ja: 語の中の記号（「2**10」「snake__case」）、前後が空白の記号、三つ以上並んだ記号（区切りや記入欄の「____」）、「__init__」のような名前、コードと引用の中の記号は指しません。
+  en: A mark inside a word ("2**10", "snake__case"), a mark with spaces on both sides, runs of three or more (dividers and blanks to fill, "____"), names such as "__init__", and marks in code or quotations are not reported.
+rewrite:
+  depth: light
+  ja:
+    direction: 太字にしたい範囲を「**」で正しく囲んでください。閉じ忘れは閉じる記号を足し、括弧の内側に置いた記号は括弧の外に出します。言葉は変えません。
+    pairs:
+      - before: 締め切りは**金曜日です。
+        after: 締め切りは**金曜日**です。
+      - before: これは**「重要」**です。
+        after: これは「**重要**」です。
+    keep:
+      - 文の言葉
+      - 太字にしたい範囲
+    avoid:
+      - 太字をやめて記号だけ消すのか、閉じるのかを、文から読み取らずに決める
+  en:
+    direction: Wrap the words meant to be bold in a matching pair of "**". Add the missing closing mark, or move a mark outside the punctuation it sits inside. Keep the words.
+    pairs:
+      - before: The deadline is **Friday.
+        after: The deadline is **Friday**.
+      - before: Mark the task **done when it ships.
+        after: Mark the task **done** when it ships.
+    keep:
+      - the words
+      - the span meant to be bold
+    avoid:
+      - deciding whether to close or drop the mark without reading the sentence

package/rules/which-that-consistency.yaml

@@ -0,0 +1,64 @@
+id: which-that-consistency
+layer: L3
+status: stable
+how_to_find: relative-pronoun-mix
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 限定の関係節の which と that が揃っていない
+  en: Restrictive "which" and "that" mixed
+
+why:
+  ja: 英語の限定の関係節（the file that contains the keys）は、that で書く人と which で書く人がいます。米国の手引きは that を勧め、英国の手引きはどちらも認めます。どちらが正しいかは決めません。一つの文書で混ざっていると、読み手は which の節が補足（読点のある非限定の節）なのかと迷います。読点を挟まない「名詞 + which / that + 動詞」だけを数え、少ないほうを指します。
+  en: 'A restrictive relative clause ("the file that contains the keys") opens with "that" for some writers and "which" for others. American guides prefer "that"; British ones accept both. chaff does not pick a side. Mixed in one document, a reader wonders whether a "which" clause is meant as an aside (the non-restrictive kind, set off by a comma). Only "noun + which/that + verb" with no comma between is counted, and the fewer form is pointed at.'
+
+message:
+  ja: 限定の関係節を「{word}」で書いています（この文書はふつう「{usual}」）
+  en: 'This restrictive clause opens with "{word}"; the document mostly uses "{usual}"'
+
+how_to_fix:
+  ja: 文書の多いほうに揃えてください。補足の節にするなら、前に読点を置いて which で書きます。
+  en: Match the rest of the document. If the clause is meant as an aside, set it off with a comma and use "which".
+
+# 少ないほうが何箇所までなら「混在」と見るか。これを超えたら、文書が使い分けている。
+levels: { strict: 4, normal: 2, relaxed: 1 }
+
+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."
+  speech: "A transcript keeps the speaker's words."
+
+group: consistency
+summary:
+  ja: 英語で、限定の関係節を which で書く所と that で書く所が混ざっている所
+  en: Restrictive clauses opened with "which" in some places and "that" in others
+
+example:
+  en:
+    before: |
+      The job that builds the site runs nightly. The script that checks links runs hourly. The task that sends mail runs daily. The file which stores the keys is encrypted.
+    after: |
+      The job that builds the site runs nightly. The script that checks links runs hourly. The task that sends mail runs daily. The file that stores the keys is encrypted.
+
+not_flagged:
+  ja: 読点のある非限定の節（the rule, which we added,）、前置詞の後ろの which（in which）、that の後ろに主語が来る節（the report that we wrote、the fact that it works）、多いほうが 3 箇所に満たない文書、少ないほうが水準の数を超える文書（使い分けている）は指しません。
+  en: 'A non-restrictive clause set off by a comma ("the rule, which we added,"), "which" after a preposition ("in which"), a "that" followed by its own subject ("the report that we wrote", "the fact that it works"), a document where the usual form appears fewer than 3 times, and one where the fewer form passes the level (used on purpose) are not reported.'
+level_meaning:
+  ja: 少ないほうの書き方が {limit} 箇所以下のとき指摘
+  en: reported when the fewer form appears {limit} times or fewer
+
+rewrite:
+  depth: light
+  en:
+    direction: Change the flagged "which" or "that" to the form the rest of the document uses. If the clause is an aside, add a comma before it and keep "which".
+    pairs:
+      - before: The file which stores the keys is encrypted.
+        after: The file that stores the keys is encrypted.
+      - before: The step which signs the build runs last.
+        after: The step that signs the build runs last.
+    keep:
+      - the clause itself and the rest of the sentence
+    avoid:
+      - changing a "which" clause set off by commas, which is an aside

package/skills/chaff/SKILL.md

@@ -32,7 +32,7 @@ choice, not a gap; turn it back on (`rules:` in `chaff.yaml`) only when the pers
 ```sh
 npx chaffjs --genre <genre> <file|dir|glob>...   # human-readable, one block per finding (a folder or glob picks up .md / .markdown / .mdx; name a .txt file directly)
 npx chaffjs . --compact                          # two lines per finding: line:col severity message, then the rule id
-npx chaffjs <file> --experimental                # also the experimental rules
+npx chaffjs <file> --experimental                # also the experimental rules (new ones, not yet measured)
 ```
 
 A run exits 1 when a finding is an `error`. It also exits 1 when it could not check anything: no file to
@@ -106,10 +106,10 @@ Use this section when asked to make a text sound less generated: 「AIっぽさ
 
 chaff marks the shapes common in generated text (group "Signs of generated text" in `npx chaffjs rules`: `ai-tell`,
 `contrast-framing`, `stock-transition`, `announcing-opener`, `colon-lead-in` (Japanese only), `assistant-residue`, and the signals
-`ai-generated-composite` reads). Most are experimental: run with `--experimental`. None of them says the text was
+`ai-generated-composite` reads). They run by default outside legal, manual, literary and spoken genres. None of them says the text was
 generated. chaff never rewrites; the rewriting is yours.
 
-**Start with the plan.** Run `npx chaffjs fix-plan <file> --experimental` (with the genre's `--genre`; `--json` to
+**Start with the plan.** Run `npx chaffjs fix-plan <file>` (with the genre's `--genre`; `--json` to
 read it as data). It prints, in the document's language:
 
 - the constraints: keep facts, numbers, conditions and names; add no fact; ask the writer instead of inventing a
@@ -140,7 +140,7 @@ repeats the body. The writer usually wants the structure changed, not only the s
 
 **Light** (only the flagged spots):
 
-1. `npx chaffjs fix-plan <file> --experimental` (or with the genre's `--genre`).
+1. `npx chaffjs fix-plan <file>` (or with the genre's `--genre`).
 2. Rewrite only the flagged spots, each by its rule's direction in the plan. Keep the meaning, numbers, conditions and
    technical constraints.
 3. Run chaff again. At most two rewrite passes.
@@ -148,7 +148,7 @@ repeats the body. The writer usually wants the structure changed, not only the s
 
 **Bold** (section by section, outline kept):
 
-1. Run chaff with `--experimental` and note the document-level signals: the `ai-generated-composite` inputs,
+1. Run chaff and note the document-level signals: the `ai-generated-composite` inputs,
    `bold-density`, `contrast-framing`, `stock-transition`, `sentence-rhythm`.
 2. Rewrite each section toward a human voice: less bold; one-line paragraphs and punchlines folded back into
    paragraphs; no "X ではありません。Y です" / "It's not X. It's Y" frames; lists turned back into sentences where the
@@ -204,7 +204,7 @@ repeats the body. The writer usually wants the structure changed, not only the s
      `chaff compare` catches an added number or name, but not added wording such as 「朝会で冗談が出るようになり」, so
      this one is yours to keep.
 5. **Check.**
-   - `npx chaffjs <old> --experimental` and `npx chaffjs <new> --experimental`: the AI signals before and after.
+   - `npx chaffjs <old>` and `npx chaffjs <new>`: the AI signals before and after.
    - `npx chaffjs outline <old> <new>`: headings, average section length, text in lists, bold, and the structure score
      and each structure measure, before and after. A restructure shows up here, not only in rule counts.
    - `npx chaffjs compare <old> <new> --distinct --allow-dropped heading --allow-added heading`: the headings are the
@@ -249,7 +249,7 @@ output before and after.
 ## Structured documents
 
 - `npx chaffjs tree <file>` shows a contract or specification as a tree of addresses (`3.2` for 第3条第2項 or
-  Section 3.2). `--experimental` adds the structure rules: references to missing provisions, numbering gaps,
+  Section 3.2). A check reads the same tree to find references to missing provisions, numbering gaps and
   terms defined twice.
 - `npx chaffjs cite <source> <quotes.json>` checks that quotations (`[{ "address", "quote" }]`) are really in
   the source; exit 1 if any is not. Use it to back every quotation you put in an answer or a summary.

package/src/cli-text.ts

@@ -31,6 +31,8 @@ const USAGE_JA = `chaff — 文章の読みにくいところを見つけます
   chaff test <file|dir>...       意味を読む検査も動かす（API key が要ります）
                                  判定役は chaff.yaml の ai_backend で選びます
   chaff init                     chaff.yaml を作る（端末ならジャンルを尋ねる。--genre <ジャンル> でも選べる）
+  chaff init --plugin <名前>     YAML だけのルールの束（chaff-plugin-<名前>/）を作る
+  chaff plugin-test [フォルダ]   プラグインの各ルールを、そのルールの例にかけて確かめる
   chaff --version                chaffjs と言語パッケージの版
   chaff eval <dir>               手元の文書で閾値を測り直す
   chaff explain <rule>           そのルールの意図と根拠を読む
@@ -74,6 +76,8 @@ const USAGE_EN = `chaff — finds what makes writing hard to read. It never rewr
   chaff test <file|dir>...       also run the checks that read meaning (needs an API key)
                                  the judge is chosen by ai_backend in chaff.yaml
   chaff init                     create chaff.yaml (asks for the genre at a terminal; --genre <genre> chooses it)
+  chaff init --plugin <name>     create a YAML rule pack, chaff-plugin-<name>/
+  chaff plugin-test [folder]     run each rule of a plugin on the rule's own example
   chaff --version                the version of chaffjs and its language packages
   chaff eval <dir>               re-measure the limits on your own documents
   chaff explain <rule>           read what a rule is for and why

package/src/cli.ts

@@ -13,8 +13,8 @@ import { runEval } from "./commands/eval.ts";
 import { runTest } from "./commands/test.ts";
 import { GENRES } from "./genre.ts";
 import { resolveGenre } from "./resolve-genre.ts";
-import { runInit } from "./init.ts";
-import { initGenre } from "./commands/init-ask.ts";
+import { runInitCommand } from "./commands/init-command.ts";
+import { runPluginTest } from "./commands/plugin-test.ts";
 import { targetsOf, withExperimental, withIncludes } from "./cli-args.ts";
 import { rulesOf } from "./custom/load.ts";
 import { renderCompact } from "./render/compact.ts";
@@ -282,19 +282,15 @@ const measureContext = (argv: readonly string[], config: Config): { config: Conf
 
 /** 分岐を数珠つなぎにせず表にする。足すときに main を太らせない。 */
 const HANDLERS: Readonly<Record<string, Handler>> = {
-  init: async (argv, config) => {
-    const ui = hostLanguage(config.language, process.env);
-    const chosen = await initGenre(flag(argv, "--genre"), ui, process.cwd());
-    if ("error" in chosen) console.error(chosen.error);
-    else runInit(process.cwd(), chosen.genre, ui).forEach((line) => console.log(line));
-    return "error" in chosen ? 1 : 0;
-  },
+  init: (argv, config) => runInitCommand((name) => flag(argv, name), argv.includes("--plugin"), hostLanguage(config.language, process.env), process.cwd()),
   genres: (_argv, config) => showGenres(config),
   rules: showRules,
   explain: (argv, config) => explain(config, argv[1], flag(argv, "--genre")),
   eval: (argv, config) => runEval(positional(argv), argv, { ...measureContext(argv, config), flag }),
   ...Object.fromEntries(Object.entries(DOCUMENT_COMMANDS).map(([name, run]): [string, Handler] => [name, (argv, config) => run(argv, treeContext(config))])),
   test: (argv, config) => runTest(positional(argv), argv, { ...measureContext(argv, config), inspect }),
+  "plugin-test": (argv, config) =>
+    runPluginTest(positional(argv)[0], { ui: hostLanguage(config.language, process.env), check: async (...args) => (await inspect(...args)).checked }),
   "fix-plan": (argv, config) =>
     runFixPlan(fixPlanTargets(argv), argv, { ...treeContext(config), check: async (path) => (await inspectAll(config, argv)(path)).checked }),
   baseline: (argv, config) => runBaseline(positional(argv), argv, config),

package/src/commands/init-command.ts

@@ -0,0 +1,13 @@
+import { runInit } from "../init.ts";
+import type { UiLanguage } from "../ui.ts";
+import { initGenre } from "./init-ask.ts";
+import { runInitPlugin } from "./plugin-init.ts";
+
+/** chaff init: chaff.yaml for a project, or with --plugin, a rule pack to start from. flag reads an option's value. */
+export const runInitCommand = async (flag: (name: string) => string | undefined, plugin: boolean, ui: UiLanguage, dir: string): Promise<number> => {
+  if (plugin) return runInitPlugin(dir, flag("--plugin"), ui);
+  const chosen = await initGenre(flag("--genre"), ui, dir);
+  if ("error" in chosen) console.error(chosen.error);
+  else runInit(dir, chosen.genre, ui).forEach((line) => console.log(line));
+  return "error" in chosen ? 1 : 0;
+};