- Home
- /
- Categories
- /
- Code Review
Code Review
Automated code review and analysis
orchestrate-multi-repo-sdks
by speakeasy-api
Use when each language SDK lives in a separate repository. Covers cross-repo workflow dispatch, PR status reporting, PR reconciliation on merge/close. Triggers on "multi-repo SDK", "separate SDK repositories", "cross-repo workflows", "SDK PR synchronization", "spec repo triggers SDK repos".
architecture-analysis
by front-depiction
"Architectural dependency analysis and impact assessment. Use for: (1) Blast radius - who depends on a service, what breaks if I change it; (2) Dependency tree - what does a service depend on (ancestors/upstream); (3) Root cause analysis - find shared dependencies when multiple services fail; (4) Architecture metrics - coupling (density), depth (diameter), connectivity; (5) Domain discovery - identify module boundaries via cut vertices; (6) Hot services - critical infrastructure with many dependents; (7) Impact assessment before changes; (8) Debugging cascading failures; (9) Identifying god services, tight coupling, deep hierarchies. Provides graph-based analysis via CLI commands: analyze, blast-radius, ancestors, common-ancestors, metrics, domains, hot-services. All agents can use this for architectural questions."
grepai-installation
by yoanbernabeu
Multi-platform installation guide for GrepAI. Use this skill when installing GrepAI on macOS, Linux, or Windows.
create-slash-commands
by cfircoo
Expert guidance for creating Claude Code slash commands. Use when working with slash commands, creating custom commands, understanding command structure, or learning YAML configuration.
razor
by blader
"Minimize local diff size against merge base for uncommitted branch work using only behavior-preserving, scope-preserving architectural reductions."
using-superpowers
by futuregerald
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
agent-wiki
by H4pplness
Persist, retrieve, and share knowledge across sessions using the agent-wiki CLI. Use this skill whenever the task involves: saving context or findings so they survive past this session, coordinating work between multiple agents via a shared task queue, building a domain knowledge base that grows over time, or reading knowledge that another agent has written. Triggers include any mention of "agent-wiki", "persist context", "knowledge base", "share between agents", "task queue", or when the user wants Claude to remember something for a future session. Also use when the user asks Claude to act as an orchestrator assigning work to specialist sub-agents.
codex-orchestrator
by indiekitai
Use when the user wants Codex App to run a supervised outer loop for multi-session development: plan bounded work, dispatch isolated worktree sessions, monitor with heartbeat and ledger truth, review/merge/push/cleanup, rescue stale tasks, and keep direct/proxy/local/blocked evidence honest.
requesting-code-review
by futuregerald
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
get-design-done
by hegemonart
"Master design pipeline for Claude Code. 5-stage workflow: Brief → Explore → Plan → Design → Verify. Run 'brief' first in any new project to capture the design problem, then 'explore' to inventory the codebase and interview for context. Invoke without arguments for status and auto-routing."
finishing-a-development-branch
by futuregerald
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
subagent-driven-development
by futuregerald
Use when executing implementation plans with independent tasks in the current session
receiving-code-review
by futuregerald
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
defi-security
by 0xlayerghost
"[AUTO-INVOKE] MUST be invoked BEFORE deploying DeFi contracts (DEX, lending, staking, LP, token). Covers anti-whale, anti-MEV, flash loan protection, launch checklists, and emergency response. Trigger: any deployment or security review of DeFi-related contracts."
crucible-writer
by forsonny
First-draft writing assistant for Crucible-planned novels. Use when author has completed planning (crucible-planner) and outlining (crucible-outliner) and wants to write the actual prose. Handles scene-by-scene drafting, style matching, continuity tracking, and hallucination prevention. Triggers on "write my novel," "draft chapter X," "start writing from my outline," "help me write my book," or when user has Crucible outline and wants prose output. Works with any Crucible-planned story.
git-pr
by dmythro
PR and MR workflows for GitHub (gh) and GitLab (glab). Covers creation,
ask-gemini
by b-open-io
This skill should be used when the user asks to "ask Gemini", "get Gemini's opinion", "have Gemini review", "improve writing style", "make less AI-sounding", "get feedback on article", "review this draft", "Nano Banana", "Gemini API help", "Gemini models", or needs a second opinion on content, writing, code, or design. Supports text questions and up to 10 images.
review-perf
by mgiovani
Perform comprehensive performance review analyzing database queries,
write-xiaohongshu
by adjfks
"Research top-performing Xiaohongshu (小红书 / XHS) image posts, analyze titles/content/comments for patterns and emotional resonance, enrich background via Firecrawl MCP, then write and publish an XHS note via Xiaohongshu MCP. Enforce hard limits: title <= 20 characters, body <= 1000 characters. Use when the user asks for 小红书笔记/种草文案/爆款标题/发布到小红书."
pubmed-cli
by drpedapati
"Search PubMed, fetch article metadata, traverse citation graphs, and look up MeSH terms from the command line. Use when: (1) Searching PubMed with Boolean/MeSH queries, (2) Fetching article details by PMID (abstract, authors, DOI, MeSH terms), (3) Finding papers that cite a given article (cited-by), (4) Finding papers cited by a given article (references), (5) Finding related articles with relevance scores, (6) Looking up MeSH vocabulary (tree numbers, scope notes), (7) Exporting citations in RIS format for Zotero/EndNote, (8) Building reproducible literature review workflows, (9) Verifying document references against PubMed for accuracy and detecting fabricated citations."
crucible-editor
by forsonny
Revision and editing assistant for Crucible-drafted novels. Use when author has completed a first draft and wants to revise, edit, or polish their manuscript. Handles developmental editing, line editing, copy editing, and final polish. Triggers on "edit my novel," "revise chapter X," "polish my manuscript," "help me edit," or when user has completed draft chapters and wants to improve them.
speccer
by schpet
"Distill rough ideas into structured project specs with issues. This skill takes unstructured input (bullet points, rough notes, transcribed ideas) and systematically breaks it down into feature domains, identifies ambiguities requiring user clarification, and produces a single structured spec document with actionable issues. Use this skill when the user wants to transform rough project ideas into well-defined specifications and issues, or when they invoke /speccer."
slack-personal
by therohitdas
Read, send, search, and manage Slack messages and DMs via the slk CLI. Use when the user asks to check Slack, read channels or DMs, send Slack messages, search Slack, check unreads, manage drafts, view saved items, or interact with Slack workspace. Also use for heartbeat Slack checks. Triggers on "check slack", "any slack messages", "send on slack", "slack unreads", "search slack", "slack threads", "draft on slack", "read slack dms", "message on slack".
ideaverse-maintenance
by mrfelton
Keep Ideaverse vaults healthy through audits, diagnostics, and maintenance workflows. Use when running vault diagnostics, detecting link rot, identifying orphan notes, finding MOC bloat, suggesting archival candidates, validating frontmatter, or generating vault health reports. Triggers on requests like "audit my vault", "find broken links", "check vault health", "what needs archiving", "find orphan notes", or "run maintenance".