perihelion-platform-context

Review a Swift change for SwiftUI body complexity, state property wrapper misuse, closure retain cycles, Swift concurrency and Core Data or SwiftData threading hazards, missing accessibility, monetary value handling, and semantic Xcode project or data model changes. Use when reviewing Swift, SwiftUI, UIKit, or iOS app code.

Review a code change for untested branches and error paths, tests that do not assert behavior, mirror tests that miss the source of truth, test-only production seams, duplicate coverage, brittle or nondeterministic tests, and behavior changes with no test changes. Use when reviewing tests, test coverage, test quality, or whether the tests prove the code works.

Carry a factory pull request through review by resolving review comments and failed checks on its existing branch, until it is ready for a person to merge or needs one to decide. Use as the action for review, review-comment, `@factory` conversation and failed-check triggers on `factory/` branches.

Ship a GitHub issue that a person labelled for Tessl the Perihelion way: read the issue and the repository, plan it with the plan skill when it needs a design, build it test-first with the build skill on the issue's own branch, and open one pull request for the issue. Stops without a trace when a person has taken the issue back.