Code Review
Automated code review and analysis
pseo-orchestrate
by lisbeth718
Orchestrate the full programmatic SEO implementation by coordinating all pseo-* skills in the correct order. Use when implementing pSEO from scratch, running the full pSEO pipeline, or when the user asks to "set up programmatic SEO" or "build pSEO pages" without specifying a single skill.
pseo-audit
by lisbeth718
Audit and assess a codebase for programmatic SEO readiness at 1000+ page scale. Use when starting a pSEO project, evaluating an existing codebase for pSEO gaps, or when the user asks to audit, assess, or review their site for programmatic SEO scalability.
first-principles-skill
by justinhuangai
用第一性原理拆解复杂的产品、商业、流程、决策和抽象命题，回到定义、 事实、假设、约束、从零重构和最小验证实验。 Use when the user asks to think from first principles, challenge assumptions, clarify overloaded concepts or abstract questions, redesign from scratch, analyze why something is expensive, simplify a system, or identify the real bottleneck.
changelog
by ratacat
Create engaging changelogs for recent merges to main branch
documentation-scraper
by ratacat
Use when needing to scrape documentation websites into markdown for AI context. Triggers on "scrape docs", "download documentation", "get docs for [library]", or creating local copies of online documentation. CRITICAL - always analyze sitemap first before scraping.
code-review
by maragudk
Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.
design-implementation-reviewer
by ratacat
"Use this agent when you need to verify that a UI implementation matches its Figma design specifications. This agent should be called after code has been written to implement a design, particularly after HTML/CSS/React components have been created or modified. The agent will visually compare the live implementation against the Figma design and provide detailed feedback on discrepancies.\n\nExamples:\n- <example>\n Context: The user has just implemented a new component based on a Figma design.\n user: \"I've finished implementing the hero section based on the Figma design\"\n assistant: \"I'll review how well your implementation matches the Figma design.\"\n <commentary>\n Since UI implementation has been completed, use the design-implementation-reviewer agent to compare the live version with Figma.\n </commentary>\n </example>\n- <example>\n Context: After the general code agent has implemented design changes.\n user: \"Update the button styles to match the new design system\"\n assistant: \"I've updated the butto..."
best-practices-researcher
by ratacat
"Use this agent when you need to research and gather external best practices, documentation, and examples for any technology, framework, or development practice. This includes finding official documentation, community standards, well-regarded examples from open source projects, and domain-specific conventions. The agent excels at synthesizing information from multiple sources to provide comprehensive guidance on how to implement features or solve problems according to industry standards. <example>Context: User wants to know the best way to structure GitHub issues for their Rails project. user: \"I need to create some GitHub issues for our project. Can you research best practices for writing good issues?\" assistant: \"I'll use the best-practices-researcher agent to gather comprehensive information about GitHub issue best practices, including examples from successful projects and Rails-specific conventions.\" <commentary>Since the user is asking for research on best practices, use the best-practices-researcher a..."
brainstorm
by maragudk
Guide for how to brainstorm an idea and turn it into a fully formed design.
collaboration
by maragudk
Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub.
audit-project-structure
by mseok
"Audit a research project's structure against the current init-project template. Reports missing directories, files, symlinks, and seed content. Report-only — except for rules sync (Phase 3.8) and permissions sync (Phase 3.11), which actively update the project."
guided-code-review
by markus1189
"Conducts an interactive, chunk-by-chunk code review of commits for a ticket or branch. Builds a mental model from story/commits, maps changes, then walks through logical groups with the reviewer. Accumulates findings for a structured final summary. Trigger: user asks for a 'guided code review'."
second-opinion
by lv416e
"Runs external LLM code reviews (OpenAI Codex or Google Gemini CLI) on uncommitted changes, branch diffs, or specific commits. Use when the user asks for a second opinion, external review, codex review, gemini review, or mentions /second-opinion."
invariant-hunter-ts
by skyosev
Audit TypeScript types for weak invariants — unnecessary casts, loose optionality, defensive ?./?? masking missing guarantees, leaky discriminated unions, and runtime checks the type system should enforce. Use when: tightening domain models, reducing type assertions, increasing type coverage, reviewing discriminated unions, or establishing a type-safety baseline before refactoring.
invariant-hunter-go
by skyosev
Audit Go code for weak invariants — unchecked errors, nil pointer risks, ignored context cancellation, unsafe type assertions, zero-value traps, panic/recover misuse, and missing validation at construction boundaries. Use when: tightening domain models, reducing panic risks, increasing error handling discipline, or establishing a safety baseline before refactoring.
deep-research
by lv416e
"Conduct comprehensive, multi-source research on any topic using web search, documentation lookup, and critical analysis. This skill should be used when users request thorough investigation, deep research, or comprehensive analysis of topics including but not limited to AI systems, technology trends, academic subjects, business strategies, or current events. 任意のトピックに対して、Web検索、ドキュメント参照、批判的分析を用いた包括的な調査を実施。徹底的な調査、詳細なリサーチ、包括的な分析が必要な場合や、AIシステム、技術トレンド、学術的テーマ、ビジネス戦略、時事問題などについて深く知りたい場合に使用。"
agent-team-review
by damianpapadopoulos
Multi-perspective parallel code review with specialist reviewers for security, quality, and spec compliance.
domain-planner
by build000r
Guide the 6-phase human-in-the-loop planning process for new domain slices spanning multiple repositories. Also orchestrates implementation when a plan is ready. Use when: - User says "let's plan the X slice" or "plan the X feature" - User wants to create a new feature spanning frontend and backend - User needs API contracts before implementation - User says "implement the X slice" or "build X" (orchestration mode) - User says "check plan quality for X" or "assess the X plan" (quality assessment mode) - User asks about planning a multi-repo feature Planning mode: Produces plan.md, shared.md, backend.md, frontend.md, flows.md, schema.mmd. Quality assessment mode: Runs assess-fix-reassess against the rubric before sign-off. Orchestration mode: Launches parallel agents per repo for scaffolding, audit, and fix loops. NOT for: bug fixes, small changes, refactoring, single-repo work.
reviewing-code
by bnadlerjr
Pragmatic code review for source code changes. Use when code has been written or modified and needs review - after implementing features, completing refactors, or before merging PRs. Focuses on catching actual problems rather than enforcing theoretical purity. Does not review documentation or non-code files.
blocklet-pr
by ArcBlock
Create standardized Pull Requests for blocklet projects. Performs lint checks, unit tests, version updates, and creates PRs following PR templates. Use /blocklet-pr or say "help me submit a PR", "create pull request" to trigger.
receiving-code-review
by bnadlerjr
Guides technical evaluation of code review feedback before implementation. Use when receiving PR comments, review suggestions, GitHub feedback, or when asked to address reviewer feedback. Emphasizes verification and reasoned pushback over blind agreement.
constant-time-analysis
by lv416e
Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.
managing-linear
by bnadlerjr
Manages Linear issues via CLI using linearis (czottmann/linearis). Use when the user mentions Linear issue identifiers (e.g., 'ENG-123'), teams, cycles, projects, labels, issue management, or workflow automation. Handles issue CRUD, comments, cycle/project/label/team/user listing, document management, file embeds, search, and GitHub/GitLab PR linking via issue identifiers.
20-andruia-niche-intelligence
by ranbot-ai
Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nich