Contact
Workflow

German Technical Writing

Enforce natural German technical register in Jira tickets, internal docs and team chat. Catches English→German anglicisms (brechen, gefangen, triggern, failen) and substitutes canonical verbs (werfen, abfangen, auslösen, fehlschlagen). Accepts Denglisch loanwords. Skips commit messages.

Latest release v1.6.2

Install

Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.

  1. Claude Code via this marketplace 
    /plugin install german-technical-writing@netresearch-claude-code-marketplace

    First add the marketplace once in Claude Code: /plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, see Claude Code plugin setup A plugin can include several skills and additional components.

  2. npx interactive skill selection 
    npx skills add https://github.com/netresearch/german-technical-writing-skill

    Requires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from skills.sh Installs skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route.

  3. composer require PHP project, as a package 
    composer require netresearch/german-technical-writing-skill

    Allow the Composer skill installer to activate and approve skill registration when prompted. Requires netresearch/composer-agent-skill-plugin Discovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup.

  4. composer skills:add PHP project, direct source 
    composer skills:add netresearch/german-technical-writing-skill

    Install and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by netresearch/composer-agent-skill-plugin Pins source repositories without a Packagist package and records them in composer.skills.lock. Runtime dependencies remain separate.

What you can do with it

  • Anti-pattern detection: ~60 false-friends catalogued — brechen, gefangen, returnen, failen, triggern, hitten, plus calqued idioms (am Ende des Tages, Low-hanging Fruit) and pseudo-anglicisms (Handy, Beamer)
  • Technical lexicon: preferred German forms with gender for Exceptions, Tests, Git, CI/CD, HTTP, Frontend, Data, and Architecture domains
  • Register enforcement: Präsens-Indikativ default, impersonal voice, no first-person in artifacts, sentence-length and compound-noun rules
  • Artifact-specific conventions: Jira ticket descriptions, Jira comments, internal German wiki/spec pages
  • Comprehension over brevity: unambiguous references instead of siehe oben, conditions and exceptions kept while shortening, sentence structure checked rather than words counted
  • Worked examples: 8 paired bad-vs-good cases with annotations

What you get back

  • Revised German technical text with clearer references, appropriate terminology and the conventions of the requested document type.

What it expects in your project

Check the source README for current examples, requirements and limitations. Open full README

Tags

  • workflow
  • productivity