Talieisin

Britfix — Documentation skill for Claude Code

Documentation community intermediate

by Talieisin - Claude outputs American spellings by default, which can have an impact on: professional credibility, compliance, documentation, and more.

How to install Britfix

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Talieisin/britfix and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Britfix does

Convert American spellings to British English. Originally created to fix the US spelling output from LLMs, but useful for anyone who needs British spellings in their documents and code.

Alternatives in Documentation

  • Doc Co-authoring — Guide users through structured workflow for co-authoring documentation 94.1k ★
  • Context7 — claude-plugins-official Up-to-date library documentation lookup 50.1k ★
  • Baoyu Skills — English 中文 宝玉分享的 Claude Code 技能集,提升日常工作效率 14.8k ★

README

Britfix

Convert American spellings to British English. Originally created to fix the US spelling output from LLMs, but useful for anyone who needs British spellings in their documents and code.

Features

  • Multiple File Types: Text, markdown, LaTeX, HTML, JSON, and code files
  • Smart Code Handling: Only converts comments and docstrings in code files, never string literals or identifiers
  • Context-Aware: Preserves quoted text like 'colorScheme' in comments (API references)
  • Interactive Mode: Review and approve changes one by one
  • Hook Integration: Automatically fix spellings when writing files

Installation

Requires [uv](https://github.com/astral-sh/uv) and optionally [just](https://github.com/casey/just).

# Install dependencies
just sync
# or: uv sync

# Build standalone binary and install to ~/.local/bin
just build && just install

Usage

# Process files
britfix --input file.txt
britfix --input "*.md" --recursive

# Process from stdin
echo "The color was analyzed" | britfix --quiet
# Output: The colour was analysed

# Interactive mode
britfix --input document.md --interactive

# Dry run
britfix --input "src/*.py" --dry-run

Options

  • --input: Input file(s) or pattern(s). If omitted, reads from stdin
  • --interactive, -i: Interactive approval mode (strategy-aware — only suggests changes in regions the strategy considers safe, e.g. comments in code files, prose in markdown). JSON files fall back to non-interactive processing
  • --dry-run: Preview changes without modifying files
  • --no-backup: Skip backup creation
  • --recursive: Process files recursively
  • --quiet: Only output corrected text (for pipelines)

File Type Strategies

Different file types are handled by different strategies, configured in `config.json`:

Strategy Extensions Behaviour
text .txt Convert everything

...