Official agent skill

Reviewing Changes

by bitwarden in bitwarden/ios

Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements.

OfficialGPL-3.0Auto-check passedDevelopment

Install Reviewing Changes

skills CLI
$ npx skills add bitwarden/ios --skill reviewing-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitwarden/ios reviewing-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitwarden/ios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/reviewing-changes .claude/skills/reviewing-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
reviewing-changes
GitHub stars
695
Token cost
~1.1k tokens
SKILL.md length
388 words
Files
13
Skills in repo
11
Repo updated
First seen
Licence
GPL-3.0

At a glance

Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements.

  • Works in 5 steps: Retrieve Additional Details → Detect Change Type → Load Appropriate Checklist → …
  • Reviewing pull requests
  • SKILL.md covers Instructions and Core Principles
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Reviewing Changes is an agent skill from bitwarden/ios, published by the product's own GitHub organization. Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements. Use when reviewing pull requests, checking commits, analyzing code changes, verifying Bitwarden coding standards, evaluating unidirectional data flow pattern, checking services container dependency injection usage, reviewing security implementations, or assessing test coverage. Automatically invoked by CI pipeline or manually for…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files (for example `checklists/bug-fix.md`, `checklists/dependency-update.md` and `checklists/feature-addition.md`).

It sits in Development, covering Code review, Test coverage and Pull requests. It works with iOS and GitHub. The repository describes itself as: Bitwarden mobile apps (Password Manager and Authenticator) for iOS. The licence is GPL-3.0.

When your agent uses it

  • Reviewing pull requests
  • Checking commits
  • Analyzing code changes
  • Verifying Bitwarden coding standards

Example prompts

  • “Use the reviewing-changes skill to perform comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style…”
  • “/reviewing-changes”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Retrieve Additional Details
  2. Detect Change Type
  3. Load Appropriate Checklist
  4. Execute Review Following Checklist
  5. Consult Reference Materials As Needed

What it can do on your machine

Read from SKILL.md and the folder at commit 6399b1d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Reviewing Changes loads about 1.1k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~139
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitwarden/ios at commit 6399b1d, republished under its GPL-3.0 licence (© bitwarden). 388 words, ~1,054 tokens.

Download SKILL.mdSave it as .claude/skills/reviewing-changes/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
reviewing-changes
description
Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements. Use when reviewing pull requests, checking commits, analyzing code changes, verifying Bitwarden coding standards, evaluating unidirectional data flow pattern, checking services container dependency injection usage, reviewing security implementations, or assessing test coverage. Automatically invoked by CI pipeline or manually for interactive code reviews.

Reviewing Changes — Bitwarden iOS

Instructions

Work systematically through each step before providing feedback. Each checklist loads only the relevant review strategy for the change type detected.

Step 1: Retrieve Additional Details

Fetch any additional context using available tools (JIRA MCP, GitHub API). If the PR title and description don't provide enough context, request:

  • A link to the JIRA ticket
  • A GitHub issue reference
  • More detail in the PR description

iOS-specific metadata checks:

  • Screenshots required for any *View.swift changes that affect visible UI — flag as ❓ if absent
  • If new *Processor.swift or *Service.swift is added with no test file, flag as ❓
Step 2: Detect Change Type

iOS-specific patterns:

  • Feature Addition: New *Coordinator.swift, *Processor.swift, *View.swift (full file-set); new screen or flow
  • Bug Fix: Targeted changes to existing *Processor.swift, *Service.swift, or *Repository.swift files
  • UI Change: Changes only to *View.swift files; no business logic changes
  • Refactoring: Renamed/restructured files without new user-visible behavior
  • Dependency Update: Changes to Mintfile, project-*.yml version references, Package.swift
  • Infrastructure: Changes to Scripts/, Configs/, .github/, fastlane/
Step 3: Load Appropriate Checklist

Based on detected type, read the relevant checklist file:

  • Dependency Update → checklists/dependency-update.md (expedited review)
  • Bug Fix → checklists/bug-fix.md (focused: fix correctness + regression test)
  • Feature Addition → checklists/feature-addition.md (comprehensive: all areas)
  • UI Change → checklists/ui-change.md (UDF compliance + accessibility + snapshots)
  • Refactoring → Full architecture check: verify behavior-preserving via reference/ios-architecture-patterns.md
  • Infrastructure → Security review + deployment impact assessment

The checklist provides: multi-pass review strategy, type-specific focus areas, what to check and what to skip.

Show full SKILL.md (155 more words)Show less
Step 4: Execute Review Following Checklist

Follow the checklist's review strategy, thinking through each pass systematically before writing feedback.

Step 5: Consult Reference Materials As Needed

Load reference files only when needed for specific questions:

  • Re-reviews (incremental) → invoke reviewing-incremental-changes agent skill; scope to changed lines only, do not flag new issues in unchanged code
  • Issue prioritization → reference/priority-framework.md (Critical vs Important vs Suggested)
  • Phrasing feedback → reference/feedback-psychology.md (questions vs commands, I-statements)
  • Architecture questions → reference/ios-architecture-patterns.md + Docs/Architecture.md
  • Security questions → reference/ios-security-patterns.md
  • Testing questions → reference/ios-testing-patterns.md
  • Style questions → reference/ios-style-patterns.md
  • Output format → examples/annotated-example.md

Core Principles

  • Priority order: Security → Correctness → Breaking Changes → Performance → Maintainability
  • Appropriate depth: Match review rigor to change complexity and risk. A dependency update doesn't need architecture review.
  • Specific references: Always use file:line_number format for precise locations
  • Actionable feedback: Say what to change and why — not just what's wrong
  • Efficient reviews: Use the change-type checklist, skip what's not relevant
  • iOS patterns: Validate UDF, Has* DI, store.binding, Sourcery mock conventions, StateProcessor subclass

© bitwarden, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files in .claude/skills/reviewing-changes of bitwarden/ios.

  • SKILL.md
  • checklists/bug-fix.md
  • checklists/dependency-update.md
  • checklists/feature-addition.md
  • checklists/ui-change.md
  • examples/annotated-example.md
  • reference/common-issues.md
  • reference/feedback-psychology.md
  • reference/ios-architecture-patterns.md
  • reference/ios-security-patterns.md
  • reference/ios-style-patterns.md
  • reference/ios-testing-patterns.md
  • reference/priority-framework.md

Open the folder on GitHubat commit 6399b1d

Compare with similar skills

Reviewing Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Reviewing Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Reviewing Changes this skillbitwarden/ios695—~1.1kAutomated safety check: PassGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Reviewerjewbetcha/opentrace1162 repos~1.1kAutomated safety check: NotesMIT
Pull Request Babysitterthedotmack/claude-mem98k—~1.1kAutomated safety check: PassApache-2.0
Renovate Actions PR Reviewbacknotprop/plannotator9.2k—~640Automated safety check: PassApache-2.0
Code Review SkillRain-kl/OpenFlare288—~2.3kAutomated safety check: NotesMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Reviewer

    jewbetcha/opentrace

    Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.

    116 GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check: notes
  • Pull Request Babysitter

    thedotmack/claude-mem

    Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.

    98k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Renovate Actions PR Review

    backnotprop/plannotator

    Reviews Renovate pull requests that bump GitHub Actions by checking pinned SHAs against upstream tags, scanning changelogs and confirming workflows stay compatible.

    9.2k GitHub stars~640 tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review Skill

    Rain-kl/OpenFlare

    Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C/.NET, Kotlin, Swift, NestJS, C/C++, and more.

    288 GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check: notes
  • Code Reviewer

    Yikai-Liao/symusic

    Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then…

    189 GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from bitwarden/ios

All 11 skills in this repo
  • Testing iOS Code

    bitwarden/ios

    Official

    Write tests, add test coverage, unit test, or add missing tests for Bitwarden iOS.

    695 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Official

    Build the Bitwarden iOS app, capture all compiler and lint warnings, categorize them into Swift 6 concurrency vs actionable, and interactively fix the actionable ones.

    695 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Build Test Verify

    bitwarden/ios

    Official

    Build the project, run tests, lint, format, spell check, generate mocks, or verify the build passes for Bitwarden iOS.

    695 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Official

    Convert a hand-written bespoke mock to a Sourcery AutoMockable-generated mock.

    695 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Official

    Evaluates a bitwarden/ios "Update SDK to" PR against the sdk-swift commit range for compile-time, runtime and serialization breaking changes, maps affected symbols to iOS call sites, and applies…

    695 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Fixing Flaky Tests

    bitwarden/ios

    Official

    Diagnose and fix flaky (intermittently failing) tests in Bitwarden iOS.

    695 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Reviewing Changes

What does Reviewing Changes do?

Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements. Reviewing Changes is an agent skill from bitwarden/ios, published by the product's own GitHub organization. Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements.

When should I use Reviewing Changes?

Reviewing Changes fits situations like: reviewing pull requests; checking commits; analyzing code changes; verifying Bitwarden coding standards.

How do I install Reviewing Changes in Claude Code?

Run `npx skills add bitwarden/ios --skill reviewing-changes -a claude-code`. Or copy the skill folder (.claude/skills/reviewing-changes in bitwarden/ios) into .claude/skills/reviewing-changes in your project. Claude Code loads it when a task matches its description.

How do I install Reviewing Changes in Codex?

Run `npx skills add bitwarden/ios --skill reviewing-changes -a codex`. Or copy the skill folder (.claude/skills/reviewing-changes in bitwarden/ios) into .agents/skills/reviewing-changes in your project. Codex loads it when a task matches its description.

Can I use Reviewing Changes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwarden/ios --skill reviewing-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reviewing-changes, .gemini/skills/reviewing-changes, .github/skills/reviewing-changes and .opencode/skills/reviewing-changes in your project.

What does Reviewing Changes need to run?

SKILL.md names no scripts, command-line tools or credentials: Reviewing Changes is instructions for the agent only.

Does Reviewing Changes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Reviewing Changes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Reviewing Changes use?

Reviewing Changes is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Reviewing Changes use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Reviewing Changes?

Skills that share tags, products or a category with Reviewing Changes: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Reviewer (jewbetcha/opentrace, 116 stars), Pull Request Babysitter (thedotmack/claude-mem, 98k stars) and Renovate Actions PR Review (backnotprop/plannotator, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reviewing Changes?

bitwarden (a GitHub organization, an official publisher) maintains it in bitwarden/ios, which has 695 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

Source: bitwarden/ios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.