This is a structured code review workflow for SwiftUI that enforces three gates before you can give feedback: anchor the files you're reviewing, consult the relevant reference docs (view composition, state management, performance, or accessibility), and cite exact file and line numbers for every issue. The checklist hits the usual SwiftUI gotchas like modifier order, StateObject versus ObservedObject ownership, lazy stacks for long lists, and accessibility labels. It's opinionated about process, which is either exactly what you need to stop vague reviews or overkill if you just want quick feedback. Works best when you're reviewing pull requests or auditing existing SwiftUI code that might have performance or accessibility problems.
npx skills add https://github.com/existential-birds/beagle --skill swiftui-code-review