Widgetkit Code Review

v1.2.1

Reviews WidgetKit code for timeline management, view composition, configurable intents, and performance. Use when reviewing code with import WidgetKit, Timel...

0· 149·1 current·1 all-time
byKevin Anderson@anderskev

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for anderskev/widgetkit-code-review.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Widgetkit Code Review" (anderskev/widgetkit-code-review) from ClawHub.
Skill page: https://clawhub.ai/anderskev/widgetkit-code-review
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install widgetkit-code-review

ClawHub CLI

Package manager switcher

npx clawhub@latest install widgetkit-code-review
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the instructions and reference material: all requirements are purely documentation/checklist-driven for WidgetKit reviews. No unrelated env vars, binaries, or installs are requested.
Instruction Scope
SKILL.md stays within the scope of source-code review: it requires reading TimelineProvider/@main Widget/AppIntentConfiguration implementations and related project artifacts (e.g., .entitlements, deployment target). The 'hard gates' require file:line artifacts from the repo and full-context reads, which is expected for rigorous code review but means the agent will inspect repository files and include code-location snippets in findings.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. The instructions reference project artifacts (entitlements, App Group ids, deployment target) which are appropriate and proportional to the WidgetKit review purpose.
Persistence & Privilege
always:false and default invocation settings are used. The skill does not request permanent presence or elevated privileges and does not modify other skills or system-wide agent settings.
Assessment
This skill is instruction-only and appears coherent for doing WidgetKit code reviews. Before using it, be aware that its hard-gate workflow requires the agent to read repository files (source files, entitlements, project settings) and include [FILE:LINE] snippets in findings — so do not run it on repos that contain secrets or credentials you don't want exposed. If you want extra caution, run reviews locally or sanitize sensitive files (keeps secrets out of source) before invoking the skill. If you need the agent to avoid copying code fragments verbatim, consider instructing it to redact or summarize findings instead.

Like a lobster shell, security has layers — review code before you run it.

latestvk972fxq0hhqs85rxgpc9jpn8jx85b75n
149downloads
0stars
2versions
Updated 6d ago
v1.2.1
MIT-0

WidgetKit Code Review

Quick Reference

Issue TypeReference
TimelineProvider, entries, reload policiesreferences/timeline.md
Widget families, containerBackground, deep linkingreferences/views.md
AppIntentConfiguration, EntityQuery, @Parameterreferences/intents.md
Refresh budget, memory limits, cachingreferences/performance.md

Review Checklist

  • placeholder(in:) returns immediately without async work
  • Timeline entries spaced at least 5 minutes apart
  • getSnapshot checks context.isPreview for gallery previews
  • containerBackground(for:) used for iOS 17+ compatibility
  • widgetURL used for systemSmall (not Link)
  • No Button views (use Link or widgetURL)
  • No AsyncImage or UIViewRepresentable in widget views
  • Images downsampled to widget display size (~30MB limit)
  • App Groups configured for data sharing between app and widget
  • EntityQuery implements defaultResult() for non-optional parameters
  • New intent parameters handle nil for existing widgets after updates
  • reloadTimelines called strategically (not on every data change)

When to Load References

  • TimelineProvider implementation or refresh issues -> timeline.md
  • Widget sizes, Lock Screen, containerBackground -> views.md
  • Configurable widgets, AppIntent migration -> intents.md
  • Memory issues, caching, budget management -> performance.md

Review Questions

  1. Does the widget provide fallback entries for when system delays refresh?
  2. Are Lock Screen families (accessoryCircular/Rectangular/Inline) handled appropriately?
  3. Would migrating from IntentConfiguration break existing user widgets?
  4. Is timeline populated with future entries or does it rely on frequent refreshes?
  5. Is data cached via App Groups for widget access?

Hard gates (before reporting)

Complete in order for each finding you intend to report. Do not advance until the pass condition is satisfied.

  1. Location artifact — The finding includes [FILE:LINE] (or a line range) copied from the current file contents; the path resolves in this repo.
  2. Scope read — You read the full surrounding implementation: the TimelineProvider (including placeholder, getSnapshot, and getTimeline when relevant), the @main Widget / widget bundle, or the configurable widget’s AppIntentConfiguration / intent types—not only a diff hunk or snippet.
  3. Platform or system claim (only if the finding depends on refresh budget, ~30MB memory guidance, Lock Screen accessory families, iOS 17+ containerBackground, App Groups data sharing, or migration from IntentConfiguration to AppIntentConfiguration) — You name one concrete artifact you inspected (for example .entitlements / App Group id in project, WidgetFamily handling in source, IPHONEOS_DEPLOYMENT_TARGET, or the exact reference subsection you used) or you drop or downgrade the finding to an open question.
  4. Protocol — Pre-report steps in review-verification-protocol are satisfied for this item (no finding if they are not).

Use the issue format [FILE:LINE] ISSUE_TITLE for each reported finding. Hard gate 4 is the full pre-report checklist for this skill’s review type.

Comments

Loading comments...