dimfeld

Run jj commit. Use when current work is ready to commit and Codex should inspect the changes, use any provided context, and create a reasonable detailed Jujutsu commit message.

Commit changes, push to remote, and create a PR skill

Create a set of phases for a large project

Read a PR review guide and review the code. Use when `review-guide.md` already exists and Codex should follow that guide, inspect the referenced changes, and append findings without overwriting prior notes.

Fix merge conflicts. Use when the current repository has unresolved conflicts and Codex should inspect both sides, trace the surrounding history, resolve the files carefully, and ask for help only when the correct resolution is unclear.

Address AI review comments in source files. Use when repository files contain AI review markers and Codex should locate them, implement the requested fixes, remove the markers, and validate the changes.

Read current_progress.md and continue from there. Use when a project has a `current_progress.md` checkpoint and Codex should restore the saved context, resume the next steps, and keep the file updated while working.

Converts "AI" comments in local files into Github PR review comments

Manages project plans with tim. Use whenever the user mentions tim, asks to "generate plan 123" (or any number), "work on plan 123", or when you are working on a tim task.

Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.

Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.

Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.