Slash Command

/hygiene

Audits project for hygiene: no secrets in repo, comments/tests presence, keychain for sensitive data, SwiftLint compliance, string catalog best practices, Xcode MCP usage. Reports issues and fixes.

Swift

iOS

code-quality

security

npx claudepluginhub fradser/dotclaude --plugin swiftui

Details

Namespaceswiftui-review/references/

Prompt Preview

# Hygiene

- If the project requires secrets such as API keys, never include them in the repository.
- Code comments and documentation comments should be present where the logic isn't self-evident.
- Unit tests should exist for core application logic. UI tests only where unit tests are not possible.
- `@AppStorage` must never be used to store usernames, passwords, or other sensitive data. Use the keychain for that.
- If SwiftLint is configured, it should return no warnings or errors.
- If the project uses Localizable.xcstrings, prefer to add user-facing strings using symbol keys (e.g. “hell...

Command Content

Other plugins with /hygiene

/audit

717

Analyzes iOS/Swift projects to suggest relevant audits or runs specified ones (e.g., memory, concurrency, accessibility, SwiftUI performance, security).

axiom

/swiftlint

Runs SwiftLint to check Swift code style, shows violations by severity, and offers auto-fix for compatible issues. Also supports strict mode.

everything-claude-code-mobile

/swift-lint

Formats and lints Swift code using swift-format on the specified path (or current directory). Launches agent with isolated context, reports summary and modified files count.

1 tool

swift-engineer

Stats

Parent Repo Stars545

Parent Repo Forks44

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Hygiene - If the project requires secrets such as API keys, never include them in the repository. - Code comments and documentation comments should be present where the logic isn't self-evident. - Unit tests should exist for core application logic. UI tests only where unit tests are not possible. - `@AppStorage` must never be used to store usernames, passwords, or other sensitive data. Use the keychain for that. - If SwiftLint is configured, it should return no warnings or errors. - If the project uses Localizable.xcstrings, prefer to add user-facing strings using symbol keys (e.g. “hell...

Hygiene

If the project requires secrets such as API keys, never include them in the repository.

Code comments and documentation comments should be present where the logic isn't self-evident.

Unit tests should exist for core application logic. UI tests only where unit tests are not possible.

@AppStorage must never be used to store usernames, passwords, or other sensitive data. Use the keychain for that.

If SwiftLint is configured, it should return no warnings or errors.

If the project uses Localizable.xcstrings, prefer to add user-facing strings using symbol keys (e.g. “helloWorld”) in the string catalog with extractionState set to "manual", accessing them via generated symbols such as Text(.helloWorld). Offer to translate new keys into all languages supported by the project.

If the Xcode MCP is configured, prefer its tools over generic alternatives. For example, RenderPreview is able to capture images of rendered SwiftUI previews for examination, and DocumentationSearch can search Apple’s documentation for latest usage instructions.

Hygiene

If the project requires secrets such as API keys, never include them in the repository.
Code comments and documentation comments should be present where the logic isn't self-evident.
Unit tests should exist for core application logic. UI tests only where unit tests are not possible.
@AppStorage must never be used to store usernames, passwords, or other sensitive data. Use the keychain for that.
If SwiftLint is configured, it should return no warnings or errors.
If the project uses Localizable.xcstrings, prefer to add user-facing strings using symbol keys (e.g. “helloWorld”) in the string catalog with extractionState set to "manual", accessing them via generated symbols such as Text(.helloWorld). Offer to translate new keys into all languages supported by the project.
If the Xcode MCP is configured, prefer its tools over generic alternatives. For example, RenderPreview is able to capture images of rendered SwiftUI previews for examination, and DocumentationSearch can search Apple’s documentation for latest usage instructions.