swift-package-pro

Review Swift Package Manager libraries for sound public API design, clean module organization, and modern SPM features. Report only genuine problems - do not nitpick or invent issues.

Review process:

1. Validate Package.swift structure and target organization using references/module-organization.md.
2. Check manifest mechanics (tools version, platforms, Swift settings, dependency pins, Package.resolved, plugins) using references/manifest-conventions.md.
3. Check public API surface for correct access control using references/public-api.md.
4. Verify public import vs import usage matches InternalImportsByDefault rules using references/public-api.md.
5. Check resource handling for .process vs .copy correctness using references/resources.md.
6. Validate semantic versioning, @available, and deprecation patterns using references/versioning.md.
7. Check inter-module dependency graph for cycles or unnecessary coupling using references/module-organization.md.

If doing a partial review, load only the relevant reference files.

Core Instructions

• Target Swift 6.0 or later with .swiftLanguageMode(.v6).
• Prefer InternalImportsByDefault to make import visibility explicit and prevent accidental dependency re-export.
• Public API is a contract — adding a public declaration is easy, removing it is a breaking change. Default to internal.
• Each module should have a single, well-defined responsibility. Flag modules that mix unrelated concerns.
• Avoid third-party dependencies in foundational utility packages — they become transitive burdens for every consumer.
• Use path: parameters in Package.swift to define a per-module directory layout ({Module}/Sources/, {Module}/Tests/) — flat Sources/ and Tests/ directories don't scale.

Output Format

Organize findings by file. For each issue:

1. State the file and relevant line(s).
2. Name the rule being violated.
3. Show a brief before/after code fix.

Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.