script/fmt and script/fmt-check dropped Markdown formatting #19

New Issue

clawbot · 2026-08-09T03:46:42+02:00

clawbot commented

2026-08-09 03:46:42 +02:00

The canonical scripts-to-rule-them-all templates in the prompts repo run prettier over Markdown:

script/fmt: yarn run prettier --write '**/*.md' --tab-width 4 --prose-wrap always
script/fmt-check: the same with --check

sfdupes replaced both bodies with gofmt only (script/fmt:9 is gofmt -s -w .; script/fmt-check:10-15 is gofmt -s -l .). Markdown formatting was dropped entirely rather than added alongside the Go formatting, and there is no .prettierrc or .prettierignore in the repo.

Consequences: make fmt cannot format this repo's Markdown, make fmt-check cannot catch unformatted Markdown, and make check passes on a README that violates the house 4-space / proseWrap: always / 80-column settings. Every Markdown change in this repo — and there are many, since the README is the authoritative specification — is currently unformatted by policy standards and nothing detects it.

Definition of done

.prettierrc and .prettierignore are copied verbatim from the prompts repo root (.prettierrc sha256 1a709149f32ac4adf4004017cf30d8f5482ccf263f414081ae8c499037691133, .prettierignore sha256 dbe0186431d09e741fe0ccddf3ac97451575ab88f94fe89353dc2e3ecb83d64b).
script/fmt runs gofmt and prettier over Markdown; script/fmt-check checks both, reporting each independently so it is clear which failed.
script/bootstrap installs prettier, pinned by hash per REPO_POLICIES — no curl | bash, no floating tag. Note the canonical template invokes it via yarn; decide and document how it is obtained here given this is a Go repo with no package.json, and keep the pinning rule intact.
The Dockerfile lint stage can still run make fmt-check, or the Markdown check is placed where CI genuinely runs it — do not let the check exist only on developer machines.
All existing Markdown in the repo is reformatted to comply, in this same commit.
make check green (including the new Markdown check) and make docker succeeds.

The canonical scripts-to-rule-them-all templates in the `prompts` repo run prettier over Markdown: - `script/fmt`: `yarn run prettier --write '**/*.md' --tab-width 4 --prose-wrap always` - `script/fmt-check`: the same with `--check` sfdupes replaced both bodies with gofmt only (`script/fmt:9` is `gofmt -s -w .`; `script/fmt-check:10-15` is `gofmt -s -l .`). Markdown formatting was dropped entirely rather than added alongside the Go formatting, and there is no `.prettierrc` or `.prettierignore` in the repo. Consequences: `make fmt` cannot format this repo's Markdown, `make fmt-check` cannot catch unformatted Markdown, and `make check` passes on a README that violates the house 4-space / `proseWrap: always` / 80-column settings. Every Markdown change in this repo — and there are many, since the README is the authoritative specification — is currently unformatted by policy standards and nothing detects it. ## Definition of done 1. `.prettierrc` and `.prettierignore` are copied verbatim from the `prompts` repo root (`.prettierrc` sha256 `1a709149f32ac4adf4004017cf30d8f5482ccf263f414081ae8c499037691133`, `.prettierignore` sha256 `dbe0186431d09e741fe0ccddf3ac97451575ab88f94fe89353dc2e3ecb83d64b`). 2. `script/fmt` runs gofmt **and** prettier over Markdown; `script/fmt-check` checks both, reporting each independently so it is clear which failed. 3. `script/bootstrap` installs prettier, pinned by hash per REPO_POLICIES — no `curl | bash`, no floating tag. Note the canonical template invokes it via `yarn`; decide and document how it is obtained here given this is a Go repo with no `package.json`, and keep the pinning rule intact. 4. The Dockerfile lint stage can still run `make fmt-check`, or the Markdown check is placed where CI genuinely runs it — do not let the check exist only on developer machines. 5. All existing Markdown in the repo is reformatted to comply, in this same commit. 6. `make check` green (including the new Markdown check) and `make docker` succeeds.

clawbot added this to the 1.0.0 milestone 2026-08-09 03:46:42 +02:00

clawbot referenced this issue

2026-08-09 03:46:53 +02:00

Vendored REPO_POLICIES.md is stale (368 lines vs the canonical 408) #20

clawbot referenced this issue

2026-08-09 03:47:54 +02:00

Land golangci-lint v2.12.2 and the canonical .golangci.yml on main #3

clawbot referenced this issue

2026-08-09 03:57:56 +02:00

Update golangci-lint to v2.12.2 with canonical config #2

clawbot referenced this issue

2026-08-09 04:01:03 +02:00