From beagle-ios
Enforces pre-report verification checklist for code reviews to eliminate false positives on unused code, missing validation, type assertions, and leaks.
npx claudepluginhub existential-birds/beagle --plugin beagle-iosThis skill uses the workspace's default tool permissions.
This protocol MUST be followed before reporting any code review finding. Skipping these steps leads to false positives that waste developer time and erode trust in reviews.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
This protocol MUST be followed before reporting any code review finding. Skipping these steps leads to false positives that waste developer time and erode trust in reviews.
Before flagging ANY issue, verify:
Before flagging, you MUST:
Common false positives:
Before flagging, you MUST:
Common false positives:
Before flagging, you MUST:
Valid patterns often flagged incorrectly:
// Type annotation, NOT forced unwrap
let data: UserData = await loader()
// Type narrowing makes this safe
if let user = data as? User {
user.name // Swift knows this is User
}
Before flagging, you MUST:
Common false positives:
Before flagging, you MUST:
Do NOT flag:
ONLY use for:
Use for:
Use for:
Use for:
These are NOT review blockers. They should be noted for the author's awareness but must not appear in the actionable issue count. The Verdict should ignore informational items entirely.
| Pattern | Why It's Valid |
|---|---|
guard let early return | Standard Swift pattern for unwrapping, not excessive nesting |
weak self in closures | Required for breaking retain cycles, not unnecessary |
@State / @Binding property wrappers | SwiftUI state management primitives |
Optional chaining (foo?.bar?.baz) | Safe access pattern, not error suppression |
as? conditional cast | Safer than force cast, correct for type narrowing |
| Pattern | Why It's Valid |
|---|---|
@StateObject in parent, @ObservedObject in child | Correct ownership pattern |
| View body computed property without caching | SwiftUI manages re-rendering efficiently |
AnyView for heterogeneous lists | Valid when @ViewBuilder or generics aren't practical |
EnvironmentObject injection | Standard SwiftUI dependency injection |
PreferenceKey for child-to-parent data | Correct alternative to callbacks for layout data |
| Pattern | Why It's Valid |
|---|---|
XCTAssertEqual without custom message | Default messages are often sufficient |
async let in test methods | Valid for concurrent test setup |
@MainActor test classes | Required when testing UI-bound code |
| Mock objects without protocol conformance | Simple test doubles are acceptable |
| Pattern | Why It's Valid |
|---|---|
+? lazy quantifier in regex | Prevents over-matching, correct for many patterns |
| Direct string concatenation | Simpler than template literals for simple cases |
| Multiple returns in function | Can improve readability |
| Comments explaining "why" | Better than no comments |
Flag force unwrap (!) ONLY IF ALL of these are true:
guard let or if let protects the access@IBOutlet (which is conventionally force-unwrapped)Flag complex View body ONLY IF:
Flag missing do/catch ONLY IF:
Result type wraps the throwing callFinal verification:
[FILE:LINE] ISSUE_TITLEIf uncertain about any finding, either: