claude-skills

Get Google Antigravity's (`agy`) code review of git changes after Claude makes edits. Trigger when user wants a second opinion on code changes ("have agy review my changes", "get code review from Google Antigravity", "review this diff with agy"), or as a final check before committing. Replaces the deprecated gemini-cli diff-review workflow.

Get Google Antigravity's (`agy`) review of Claude's implementation plans. Trigger when user wants a second opinion on a plan ("have agy review this plan", "get a second opinion from Google Antigravity", "critique this plan with agy"), or after Claude creates a plan file that needs validation before implementation. Replaces the deprecated gemini-cli plan-review workflow.

Real-time web research using Google Search via Google's Antigravity (`agy`) CLI — the replacement for the deprecated `gemini-cli`. Trigger when user needs current information ("search with agy", "search with Google Antigravity", "find current info about X with agy", "what's the latest on Y"), library/API research, security vulnerability lookups, or comparisons requiring recent data.

Deep architectural analysis of the current workspace using Google Antigravity (`agy`). Trigger when the user needs an architecture overview ("analyze this codebase with agy", "map dependencies with Google Antigravity"), is onboarding to unfamiliar code, exploring legacy systems, or hunting technical debt. Replaces the deprecated gemini-cli `codebase_investigator` workflow.

Codebase analysis via the Codex MCP server with a read-only sandbox. Trigger when user needs architecture overview ("analyze this codebase with Codex", "have Codex map dependencies"), onboarding to unfamiliar code, understanding legacy systems, or identifying technical debt.

Get Codex's code review of git changes via the Codex MCP server. Trigger when user wants a second opinion on code changes ("have Codex review my changes", "get code review from Codex", "review this diff with Codex"), or as a final check before committing.

Get Codex's review of Claude's implementation plans via the Codex MCP server. Trigger when user wants a second opinion on a plan ("have Codex review this plan", "get second opinion from Codex", "critique this plan with Codex"), or after Claude creates a plan file that needs validation before implementation.

This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions", "declarative-friendly"

This skill should be used when working with SwiftData — @Model definitions, @Query, @Relationship, ModelContext, ModelContainer, schema migration, Swift 6 concurrency, performance optimization, or architecture review. Also triggers on: "SwiftData audit", "@Model issues", "SwiftData crashes", "predicate problems", "background context patterns", "N+1 queries", "SwiftData vs SQLiteData vs GRDB", "CloudKit sync with SwiftData", "SwiftData migration fails", or "SwiftData migration diagnostics". Covers auditing existing code, writing new SwiftData code, migration debugging, and architecture review.

This skill should be used when the user asks "what's wrong with this video", "why does this video look bad", "detect video artifacts", "find quality issues", "video has artifacts", "identify compression artifacts", or wants to diagnose specific quality problems in a video file.

This skill should be used when the user asks "what does this mediainfo mean", "explain this video format", "what is BT.709", "what is H.264", "container vs codec", "why is this 10bit", "what does limited range mean", or wants educational explanations of video technical concepts.

This skill should be used when the user asks "check frame rate", "is this CFR or VFR", "video has duplicate frames", "video stutters", "frame rate issues", "why does video judder", or wants to analyze frame rate characteristics and detect timing problems.

This skill should be used when the user asks "is this real HDR", "check HDR metadata", "fake HDR", "is this Dolby Vision legitimate", "HDR vs SDR", "check HDR peak brightness", or wants to verify whether HDR content is genuine or inverse tonemapped from SDR.

This skill should be used when the user asks "compare these videos", "which source is better", "compare blu-ray vs web", "which release should I use", "compare video quality", or needs to evaluate multiple versions of the same content to determine which has better quality.

This skill should be used when the user asks "check subtitles", "audit subs", "subtitle font issues", "ASS vs SRT", "missing fonts", "subtitle timing", or wants to analyze subtitle tracks for issues like missing fonts, timing problems, or format limitations.

This skill should be used when the user asks "is this interlaced", "detect telecine", "video has combing", "should I deinterlace", "3:2 pulldown", "inverse telecine", or sees horizontal lines/combing artifacts in video and wants to understand if the content is truly interlaced or telecined.

This skill should be used when the user asks to "audit this video", "analyze video quality", "check this video file", "is this video good quality", "should I reencode this", "what format is this video", or wants to understand a video file's technical properties and quality before working with it.

Deep architectural analysis using Gemini's codebase_investigator tool. Trigger when user needs architecture overview ("analyze this codebase", "map dependencies"), onboarding to unfamiliar code, understanding legacy systems, or identifying technical debt.

Get Gemini's code review of git changes after Claude makes edits. Trigger when user wants a second opinion on code changes ("have Gemini review my changes", "get code review from Gemini", "review this diff"), or as a final check before committing.

Get Gemini's review of Claude's implementation plans. Trigger when user wants a second opinion on a plan ("have Gemini review this plan", "get second opinion", "critique this plan"), or after Claude creates a plan file that needs validation before implementation.

Real-time web research using Gemini's Google Search. Trigger when user needs current information ("search with Gemini", "find current info about X", "what's the latest on Y"), library/API research, security vulnerability lookups, or comparisons requiring recent data.

Deduplicate and consolidate CLAUDE.md memory files. Trigger when user says "condense my CLAUDE.md files", "deduplicate CLAUDE.md", "clean up my memory files", or "consolidate my instructions". Removes redundancy within files and across the file hierarchy.

Analyze recent conversation to identify improvements for CLAUDE.md memory files. Trigger when user says "reflect on this session", "reflect on this conversation", "reflect on this code", or "improve CLAUDE.md by reflecting on this session". The verb "reflect" combined with a session/conversation/code subject is the key trigger.

GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").

GitHub issue management using GitHub CLI. Trigger when user wants to list issues ("show open issues"), view issue details ("view issue 456"), create issues ("create an issue", "file a bug"), or edit/close issues ("close issue", "add label to issue").

Pull request operations using GitHub CLI. Trigger when user wants to list PRs ("show open PRs"), view PR details ("view PR 123"), create PRs ("create a pull request"), review/merge PRs ("merge PR", "approve PR"), or view PR diffs ("show PR diff", "what files changed in PR").

Repository information using GitHub CLI. Trigger when user wants to view repository details ("show repo info", "what's this repo about"), list repositories ("list my repos", "show repos for user"), or check repository metadata ("stars", "languages", "topics").

Fetch raw file content from GitHub URLs. Trigger when user shares a GitHub file link (https://github.com/user/repo/blob/main/file.go) and wants to view the source code. Avoids HTML/JS clutter from WebFetch.

Display plugin versions from marketplace.json. Use when user asks to "audit versions", "show plugin versions", "list marketplace versions", or wants to see the current state of plugin versioning.

Bump a plugin version in marketplace.json using semantic versioning. Use when user asks to "bump version", "increment version", "release new version", or after making changes that warrant a version update.

Bump a plugin version in its plugin.json file using semantic versioning. Use when user asks to "bump plugin version", "increment plugin version", or after making changes to a plugin that warrant a version update.

Review Go code for adherence to Go Style Guide. Use when the user requests a code review of completed work, pull requests, or feature branches in Go projects. Focuses on critical bugs, race conditions, and important maintainability issues. Trigger phrases include "review this Go code", "check against style guide", "review my PR", or "review the work done so far".