@cocoanetics/swiftbutler
AAnalyze, syntax-check, reindent, and distribute Swift source code with the SwiftButler CLI. Use when working with Swift files or packages and you need a compact API overview (`analyze` in interface/json/yaml/markdown), fast syntax validation (`check`), indentation cleanup with spaces or tabs (`reindent`), or to split large Swift files into declaration-based output files (`distribute`). Also use when setting up SwiftButler from Homebrew or verifying the installed CLI version.
Install
agr install @cocoanetics/swiftbutler --target claudeWrites 8 files into .claude/skills/, pinned to git-9f0d4d9f.
- .claude/skills/swiftbutler/.clawdhubignore
- .claude/skills/swiftbutler/.gitignore
- .claude/skills/swiftbutler/CLI.md
- .claude/skills/swiftbutler/LICENSE
- .claude/skills/swiftbutler/Package.resolved
- .claude/skills/swiftbutler/Package.swift
- .claude/skills/swiftbutler/README.md
- .claude/skills/swiftbutler/SKILL.md
Document
name: swiftbutler
version: 1.0.0
description: >
Analyze, syntax-check, reindent, and distribute Swift source code with the
SwiftButler CLI. Use when working with Swift files or packages and you need a
compact API overview (analyze in interface/json/yaml/markdown), fast syntax
validation (check), indentation cleanup with spaces or tabs (reindent), or
to split large Swift files into declaration-based output files (distribute).
Also use when setting up SwiftButler from Homebrew or verifying the installed
CLI version.
homepage: https://github.com/Cocoanetics/SwiftButler
metadata:
openclaw:
emoji: "🧹"
requires:
bins: ["butler"]
install:
- id: brew
kind: brew
formula: cocoanetics/tap/swiftbutler
bins: ["butler"]
label: "Install SwiftButler via Homebrew"
SwiftButler
Use butler to reduce Swift source into a more manageable working surface.
Setup
Install via Homebrew:
brew install cocoanetics/tap/swiftbutler
Verify:
butler --version
For local development from a checkout:
swift build
.build/debug/butler --version
Core Rules
- Prefer
analyzewhen an agent needs API shape, not full implementation details. - Prefer
--format yamlor--format jsonwhen the result will be parsed or reused. - Prefer
checkfor fast validation loops beforeswift build. - Use
reindentto normalize indentation in place; choose exactly one of--spaces <n>or--tabs. - Use
distributebefore targeted edits when a generated file has become too large or noisy.
Fast Command Map
Analyze Swift APIs
# Default interface-style output
butler analyze Sources/MyModule
# Public API only
butler analyze Sources/MyModule --visibility public
# Recursive YAML output for tooling
butler analyze Sources --recursive --format yaml
# Write structured output to a file
butler analyze Sources --recursive --format yaml --output api.yaml
Supported formats:
interfacejsonyamlmarkdown
Syntax-check Swift quickly
butler check Sources --recursive
butler check Sources --recursive --json
butler check Sources --recursive --json --pretty
butler check Sources --recursive --format markdown --show-fixits
Reindent with spaces or tabs
# Default: 3 spaces
butler reindent Sources --recursive
# Explicit spaces
butler reindent Sources --recursive --spaces 2
butler reindent Sources --recursive --spaces 4
# Tabs instead of spaces
butler reindent Sources --recursive --tabs
# Preview without modifying files
butler reindent Sources --recursive --tabs --dry-run
Notes:
--spaces <n>accepts values from1to16.--tabsand--spaces <n>are mutually exclusive.- Without
--tabs, the default is--spaces 3.
Distribute large files into smaller ones
# Split one large generated file
butler distribute Generated.swift
# Preview recursive distribution
butler distribute Sources/Generated --recursive --dry-run
# Write distributed files to a separate directory
butler distribute Sources/Generated --recursive --output SplitSources
When to Use Which Command
- Use
analyzeto hand an LLM a compact view of types, functions, properties, and docs. - Use
checkinside generation or repair loops for immediate syntax feedback. - Use
reindentafter generated or patched code has inconsistent indentation. - Use
distributewhen one large Swift file should become declaration-sized files that are easier to inspect and edit.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-9f0d4d9f644d2026-07-31