fa/breadcrumb-the-shire
1
0
Fork 1
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
545bcc789bc4797ec69d51d1d8f5a6b4fbcb647f
breadcrumb-the-shire/.agents/skills/starterkit-php-style-ci/SKILL.md
fs 545bcc789b docs: replace ASCII umlaut fallbacks with proper äöüß across all .md 
Most German docs were written with `ue`/`ae`/`oe`/`ss` ASCII fallbacks
(`fuer`, `aenderung`, `koennen`, `gemaess`) — relic from older toolchain
constraints. Replaced 237 occurrences across 38 .md files with proper
umlauts and ß so the docs read naturally.

Substitutions are constrained to plain prose: fenced code blocks
(```...```), inline code spans (`...`), markdown link targets `[..](..)`,
and HTML comments are preserved verbatim. Path references like
`docs/howto-erste-aenderung.md` keep their original (umlaut-replaced)
filenames — only the surrounding prose is normalised.

Tool: bin/fix-md-umlauts.py (idempotent — no-op on already-clean files).
Re-runnable if ASCII fallbacks creep back in via copy-paste.

Doc-link-check + doc-drift-check stay green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-29 09:57:22 +02:00

1.4 KiB
Raw Blame History

name, description
name description
starterkit-php-style-ci Standard-Skill für PHP Coding-Style im Starterkit (php-cs-fixer, dry-run in CI, lokaler fix/check workflow). Verwenden bei Style-Einführung, CI-Checks oder grossen Format-Diffs.

Starterkit PHP Style CI

Ziel

Coding-Style prüfbar, reproduzierbar und regressionsarm machen.

Wann verwenden

  1. Einführung oder Nachschaerfung von Style-Regeln.
  2. CI-Dry-Run für Style-Checks.
  3. Aufraeumen grosser Style-Diff-Wellen.

Verbindliche Regeln

  1. MUST vendor/bin/php-cs-fixer fix --config=tools/php-cs-fixer/.php-cs-fixer.dist.php --dry-run --diff --verbose für nicht-mutierende Prüfung nutzen (Convenience-Alias: composer cs:check).
  2. MUST composer cs:fix nur bewusst und mit Diff-Kontrolle ausführen.
  3. MUST Style-Check vor Merge gruen halten (lokal und optional CI).
  4. MUST nach groesseren Fixes mindestens phpunit und phpstan laufen lassen.
  5. MUST NOT manuell Einzelstellen formatieren, wenn der Fixer sie zentral loesen kann.

Workflow

  1. Baseline erfassen: vendor/bin/php-cs-fixer fix --config=tools/php-cs-fixer/.php-cs-fixer.dist.php --dry-run --diff --verbose.
  2. Falls nötig fixen: composer cs:fix.
  3. Diff fokussiert prüfen (Imports, Braces, Nebenwirkungen).
  4. Qualitaetsgates laufen lassen.
  5. CI-Dry-Run konfigurieren oder validieren.

Referenzen

  • Lokaler Workflow: references/style-workflow.md
  • CI Dry Run: references/ci-dry-run.md
Reference in New Issue View Git Blame Copy Permalink