swiftzilla/swift_review
skills/swift_review/SKILL.md
Use this skill for PR safety and risk analysis. It analyzes the risk and blast radius of a PR using git diff. Use before committing changes, reviewing pull requests, or assessing the impact of code modifications — even if they don't mention "review" but describe checking change safety or understanding what a diff affects.
$ install --global
skillsauthnpx skillsauth add swiftzilla/skills swift_reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 2:21 AM19.0s2 files scanned
SKILL.md
- name:
- swift_review
- description:
- >-
- license:
- Proprietary
- compatibility:
- Requires macOS 14+. Universal macOS executable (arm64 + x86_64).
- author:
- SwiftZilla
- version:
- 21eb566
Swift Review: PR Safety & Risk Analysis
Analyze the semantic impact of your changes and catch potential regressions before they land.
Commands
# Review diff against current HEAD
scripts/swift_review
# Review diff against a specific target branch
scripts/swift_review --target <BRANCH>
Workflow
- Analyze: Run
scripts/swift_reviewto see the semantic impact of your changes - Assess risk: Look for "High Impact" warnings (high Fan-In files) — these are the most dangerous changes to get wrong
- Verify: For each file mentioned in the "Impacted Files" list, run its specific tests to confirm nothing broke
- Proceed: Only commit when high-risk areas are covered by tests
Gotchas
- Always run this BEFORE committing — not after. The tool analyzes uncommitted changes by default.
- "High Impact" means the file has many dependents (high Fan-In). Changes to these files have a larger blast radius and need more careful testing.
- If no tests exist for an impacted file, flag it for manual review — the tool cannot verify correctness without tests.
- When using
--target, make sure the target branch is up to date locally — stale branches produce misleading diffs.
Related Skills
swiftzilla/swiftzilla
tools
VerifiedTrustedCommunity
Use this skill when you need expert Swift/iOS architectural guidance, semantic codebase analysis, or PR impact reviews. It provides a senior mentor layer for Swift (SwiftUI, UIKit, Combine, Concurrency) and a semantic engine to query local code context. Trigger this skill to: 1. Validate architectural patterns before implementation using 'ask'. 2. Find and map local code dependencies using 'context'. 3. Analyze the risk and blast radius of a PR using 'review'. 4. Generate system overviews for onboarding using 'onboard'. 5. Troubleshoot runtime crashes with semantic LLDB tools using 'debug'. Activate even if specific keywords are missing but the intent is improving Swift code quality or understanding project structure.
4SKILL.mdUpdated Apr 15, 2026
swiftzilla/swift_testing
development
VerifiedTrustedCommunity
Swift Testing framework for unit tests, integration tests, and async testing with modern syntax.
4SKILL.mdUpdated Apr 15, 2026
swiftzilla/swift_swiftui
development
VerifiedTrustedCommunity
SwiftUI framework concepts including property wrappers, state management, and reactive UI patterns.
4SKILL.mdUpdated Apr 15, 2026
swiftzilla/swift_style
development
VerifiedTrustedCommunity
Swift style guidelines covering naming conventions, code organization, and best practices for writing idiomatic Swift code.
4SKILL.mdUpdated Apr 15, 2026