swiftformat and swiftlint are needed for building Peekaboo

[thecocoa]

I had to:

brew install swiftlint
brew install swiftformat

to begin building OpenClaw on macOS 27 development beta.

I didn't see these listed as pre-requisites.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 30, 2026, 3:38 AM ET / 07:38 UTC.

Summary
Keep this issue open: current main still omits SwiftLint and SwiftFormat from the source-build prerequisites, while the exact documentation correction is actively owned by #299. Likely related people: Peter Steinberger is a low-confidence routing candidate for the source-build and package-tooling surface.

Reproducibility: yes. from source: current docs/building.md omits both tools while package.json directly invokes swiftlint and swiftformat; no local build run is needed to establish the documentation gap.

Next step
The exact correction is already represented by the open linked pull request, so a separate repair job would duplicate contributor work.

Review details

Best possible solution:

Review and land the narrow documentation update in #299; after it merges, the issue can close through its linked closing reference.

Do we have a high-confidence way to reproduce the issue?

Yes, from source: current docs/building.md omits both tools while package.json directly invokes swiftlint and swiftformat; no local build run is needed to establish the documentation gap.

Is this the best way to solve the issue?

Yes: the linked one-file documentation PR is the narrowest maintainable fix because it documents existing tooling without changing build scripts or project behavior.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 8448599ab899.

Label changes

Label justifications:

• P3: This is a small developer-documentation correction with no runtime behavior change.
• impact:ux-friction: Developers following the source-build guide may need trial-and-error installation before lint or format commands work.

Evidence reviewed

What I checked:

• Current documentation omission: docs/building.md lists macOS, Swift, Node.js, and pnpm prerequisites but does not list SwiftLint or SwiftFormat, so current main does not yet document the reported dependency. (github.com) (docs/building.md:237, 8448599ab899)
• Tooling dependency: The package scripts invoke swiftlint lint --config .swiftlint.yml and swiftformat ., confirming that the omitted tools are part of the documented pnpm validation path. (github.com) (package.json:461, 8448599ab899)
• Open implementation candidate: The provided GitHub context shows docs: document SwiftLint and SwiftFormat prerequisites #299 is open, changes one documentation file, explicitly closes this issue, and adds the missing prerequisites without altering build behavior. (docs/building.md:237, 14ed4c1efd69)
• Repository policy fit: The checked repository guidance places documentation in docs/, identifies pnpm run lint and pnpm run format as normal validation commands, and asks PRs to mention documentation updates when behavior changes. (raw.githubusercontent.com) (AGENTS.md:1, 8448599ab899)

Likely related people:

• Peter Steinberger: The package manifest identifies Peter Steinberger as the package author, and this issue concerns the project-level source-build workflow and its pnpm tooling commands rather than a single Swift module. (role: adjacent project and package-tooling owner; confidence: low; commits: 8448599ab899; files: package.json, docs/building.md)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.