Skip to content
TrustedSkillsbeta
Back to all skills

Swift Code Review

Checked
existential-birds·vlatest·backend·Apache-2.0

Helps with Swift, code review as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add existential-birds/beagle --skill swift-code-review -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

existential-birds

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 existential-birds/beagle at d1a74899fb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d1a74899fb
Manifest
plugins/beagle-ios/skills/swift-code-review/SKILL.md
Scanned
5 files, 636 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The swift-code-review skill enables AI agents to analyze Swift source code for syntax errors, logical flaws, and adherence to best practices. It provides immediate feedback on readability, performance issues, and potential bugs within iOS or macOS applications.

When to use it

  • Before merging pull requests in a Swift-based repository to catch regressions early.
  • During the development phase to validate complex algorithms or data handling logic.
  • When refactoring legacy codebases to ensure modern Swift compatibility.
  • To audit security vulnerabilities in network or authentication modules.

Key capabilities

  • Identifies syntax errors and type mismatches in Swift files.
  • Suggests improvements for code readability and maintainability.
  • Flags performance bottlenecks such as inefficient loops or memory leaks.
  • Enforces adherence to Apple's coding conventions and style guides.

Example prompts

  • "Review this Swift file for potential race conditions in the network layer."
  • "Analyze the provided view model for memory retention issues with closures."
  • "Check if this new feature implementation follows SwiftUI best practices."

Tips & gotchas

Ensure the AI agent has access to the full project context, as isolated code snippets may miss dependency-related errors. While effective for static analysis, always verify critical logic changes manually before deployment.