Loading...
Loading...
Found 582 Skills
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Golang code style, formatting and conventions. Use when writing code, reviewing style, configuring linters, writing comments, or establishing project standards.
Interactive plan and diff review for AI coding agents. Visual browser UI for annotating agent plans — approve or request changes with structured feedback. Supports code review, image annotation, and auto-save to Obsidian/Bear Notes.
Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.
Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.
Audit and improve SQL quality systematically — catch performance smells in raw SQL, ORM-generated queries, schema/modeling decisions, migrations, or PR diffs, explain the database-level impact, give a corrected version, and make the tradeoff explicit. Generic by design: no project, domain, ORM, or language config — any context it needs (is this table transactional? is the scan intentional? what volume is expected?) is raised during analysis, never assumed. Reach for it whenever someone writes, reviews, or optimizes a query or data-access code — "review this query", "why is this slow", "check my migration", "is this index right", or when you see N+1, SELECT *, a cartesian/row explosion, three-plus joins, a missing date filter on a growing table, OFFSET pagination, LIKE '%term%', NOT IN with nullable columns, an unindexed ORDER BY, an unbounded list, or a long transaction — even when they never say the word "SQL". Use it both to validate new code and designs and to audit existing ones.
Applies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Validate whether an implementation matches its stated goal. Use this skill when a skill or agent wants a second opinion on its own output, when the user says "check this implementation", "validate what you did", "is this correct?", "review the output", or "did you do this right?". Also spawned automatically as a subagent by other skills (memory-bridge, daily-update) to self-check their outputs before presenting to the user. Returns a structured pass/warn/fail verdict with specific actionable issues.
Detect and remediate Go anti-patterns: premature interface abstraction, goroutine overkill, context soup, error wrapping mistakes, generic abuse, channel misuse, unnecessary function extraction, and interface pollution. Use when reviewing Go code for quality, detecting over-engineering, or when user mentions "anti-pattern", "code smell", "Go mistake", or "bad Go". Do NOT use for feature implementation, performance optimization without a code smell, or non-Go languages.
Iteratively review changes, run automated tests, and apply targeted fixes until issues are resolved (or a stop condition is reached).