Swift Diagnostics
CheckedQuickly identifies and suggests fixes for common frontend code errors and performance bottlenecks.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add johnrogers/claude-swift-engineering --skill swift-diagnostics -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
johnrogers
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned johnrogers/claude-swift-engineering at 1dc2cf4d02.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1dc2cf4d02
- Scanned
- 6 files, 1,164 lines
About this skill
swift-diagnostics
What it does
This skill enables AI agents to analyze Swift code and generate detailed diagnostic reports. It helps identify syntax errors, type mismatches, and potential runtime issues directly within the development workflow.
When to use it
- Debugging complex Swift modules where standard compiler output is unclear.
- Reviewing third-party libraries for compatibility with your specific iOS version.
- Validating code changes before committing to a repository to prevent build failures.
- Generating human-readable explanations for obscure error messages in Xcode or CLI builds.
Key capabilities
- Parses Swift source files to detect structural and logical errors.
- Provides actionable suggestions for fixing identified issues.
- Integrates with existing CI/CD pipelines for automated code quality checks.
- Supports both iOS and macOS specific Swift frameworks.
Example prompts
- "Analyze this Swift file for any type safety violations or memory management leaks."
- "Explain why the compiler is throwing an error on line 42 of my NetworkManager class."
- "Generate a diagnostic report for this new SwiftUI view component before I run the build."
Tips & gotchas
Ensure your AI agent has access to the full project context, including imported frameworks and configuration files, for accurate diagnostics. This skill is most effective when used alongside a local Swift compiler instance to validate real-time build errors.