This skill should be used when the user asks to "clone a repo", "fetch code from github", "get external code", "look at a repo", or needs…
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals.
Use when the user wants to close out a finished PR (`/close-pr`, "close this PR", "merge and clean up").
Use when a coding task must be completed against explicit acceptance criteria with minimal user re-intervention across implementation…
Use when choosing between CloudKit vs iCloud Drive, implementing reliable sync, handling offline-first patterns, or designing sync…
Help backport PRs to release branches using the backport CLI tool.
Guide to migrating an existing Capacitor iOS app from CocoaPods to Swift Package Manager (SPM).
Reverse engineer Cocos Creator 2.x / 3.x game builds.
Use when running TypeScript compile check on Cocos Creator 3.x project.
Use when the user mentions Codable review, JSON encoding/decoding issues, data serialization audit, or modernizing legacy code.
Writes production code that satisfies stack-context standards on the first pass: interface-first design, backward-compatibility checks…
Use this skill when the user wants to refactor code or improve documentation structure without changing external behavior.
Find and eliminate code duplication with DRY refactoring strategies
Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview.
Systematic approach to refactoring code for improved maintainability, performance, and clarity while preserving functionality
Augments human code review by summarizing changes, surfacing key review questions, assessing test coverage, and identifying low-risk…
Load a 3D model from an OBJ file, create a textured mesh with mipmaps, and render with a fly-around camera.
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Code review of changes on the current branch.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review…
Use when opening a PR for review or when receiving review feedback.