古适模版模版

or: npm install -g agent-style # Node users

or: npx --yes agent-style@0.3.6 <subcommand> # no install needed

```

Skill-host path (Claude Code / Anthropic Skills): install once, then /style-review <file>

agent-style enable style-review # auto-detects active skill-capable surfaces

3. Bundled via [anywhere-agents](https://github.com/yzhao062/anywhere-agents) (zero-config)

If your project already uses anywhere-agents — a maintained agent configuration for Claude Code, Codex, and other AGENTS.md-compliant tools — agent-style is the default rule pack: no enable step needed. The anywhere-agents bootstrap fetches agent-style's canonical rules at a pinned git tag and composes them into your project's AGENTS.md automatically on every run.

pipx run anywhere-agents   # Python path
npx anywhere-agents        # Node.js path

Opt out by adding rule_packs: [] to agent-config.yaml at your project root; pin to a specific ref or swap for a fork via rule_packs: - name: agent-style\n ref: <tag>. See anywhere-agents rule-pack composition docs for the full contract.

CLI path (works anywhere pip/npm runs; no skill host needed):

agent-style review DESIGN.md # human-readable audit agent-style review DESIGN.md --audit-only # machine-readable JSON agent-style review --compare a.md b.md # A/B delta per rule

**What happens on `/style-review DESIGN.md`** (skill path):

1. Deterministic audit of the file against all 21 rules.
2. Skill asks: *"produce a polished draft at `DESIGN.reviewed.md`?"*
3. On yes: writes a revised copy beside the original and shows the diff. **Source file is never touched.**

**What you get from `agent-style review DESIGN.md`** (CLI path): the same deterministic audit — mechanical + structural detectors for em-dashes, jargon, transition openers, clichés, contractions, sentence length, bullet overuse, same-starts, paragraph closers. Semantic rules (vague claims, unsupported claims, etc.) return `status: "skipped"` because they need a skill host's model. No polish from the plain CLI.

See the [Does It Work?](#does-it-work) section above for measured mechanical-violation reductions on Claude Opus 4.7 and OpenAI GPT-5.4.

<details>
<summary><b>Skill workflow in detail (what the SKILL.md tells Claude Code to do)</b></summary>
<br>

1. Shells out to `agent-style review --audit-only DESIGN.md` for the deterministic audit (same JSON as the CLI path).
2. Adds semantic judgment via the host model for the 7 rules that need context-aware reasoning: RULE-01 curse of knowledge, RULE-03 vague language, RULE-04 needless words, RULE-08 uncalibrated claims, RULE-11 stress position, RULE-F term drift, RULE-H citation discipline.
3. Merges deterministic + semantic scorecard; reports per-rule counts and first 5 violations each.
4. Asks the user: *"produce a polished draft at DESIGN.reviewed.md?"*
5. On yes, composes a revision prompt using `references/revision-prompt.md` with hard invariants:
   - **No new facts, metrics, citations, links, or code behavior** not in the source.
   - Preserve Markdown structure (code fences, tables, frontmatter, links, heading levels, list nesting).
   - Preserve meaning and length budget.
6. Writes `DESIGN.reviewed.md` alongside `DESIGN.md`.
7. Re-audits the revised draft; shows before → after scorecard and `diff DESIGN.md DESIGN.reviewed.md`.

Source file is never touched. You merge hunks from the `.reviewed.md` by hand.

</details>

<details>
<summary><b>Uninstall</b></summary>
<br>

Per-tool disable:

For `style-review`, disable reads `.agent-style/skills/style-review/manifest.json`, removes only files whose current sha256 still matches (leaves user-edited files alone and reports them as `drifted`), and cleans up empty directories. Never touches `.agent-style/RULES.md` or other-tool adapters.

Full cleanup of the shared `.agent-style/` data (after disabling every tool you enabled):

</details>

<details> <summary><b>Self-verification probe</b></summary> <br>

After running agent-style enable <tool>, ask your agent:

Is agent-style active?

Expected reply:

agent-style v0.3.6 active: 21 rules (RULE-01..12 canonical + RULE-A..I field-observed); full bodies at .agent-style/RULES.md.

For style-review specifically, ask:

Is style-review active?

Expected reply:

style-review active: audit 21 rules (deterministic: RULE-B, D, G, I, 12, 05, 06, A, C, E; semantic via host: RULE-01, 03, 04, 08, 11, F, H); workflow at skills/style-review/SKILL.md.

If the version string or rule count is missing, the file is on disk but not in your agent's active context. Check that your tool's instruction-file reload behavior picked up the new content (some tools require a session restart).

</details>

<details> <summary><b>Complementary Post-Hoc Linting</b></summary> <br>

This repo is read at generation time. For a linter that runs over committed prose in CI, see ProseLint; per-rule check-ID mappings are in enforcement/proselint-map.md. Vale users can plug ProseLint via its existing style-pack ecosystem.

</details>