Loading...
Loading...
Found 1,231 Skills
Guide for simplifying and refining code after coding sessions. Use when cleaning up complex code, reviewing PRs for readability, or applying consistent refactoring patterns.
Perform SGLang code review in the style of human maintainers by consulting the 2024-2025 non-agent PR review corpus, including inline code snippets, original multilingual comments, and discussion threads. Use when reviewing SGLang PRs, diffs, patches, or local changes for correctness, tests, performance, GPU/runtime risks, API compatibility, and maintainability.
Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.
Validate an implemented React Doctor rule before merge. Use after focused tests pass to review detector correctness, inspect open-source hits, run pull request parity, add regression coverage, prepare a changeset, write pull request copy, or address review findings.
Review a GitHub pull request using Alan's GitHub MCP tools
This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
JavaScript style and best practices based on Google's official JavaScript Style Guide. This skill should be used when writing, reviewing, or refactoring JavaScript code to ensure consistent style and prevent common bugs. Triggers on tasks involving JavaScript, ES6, modules, JSDoc, naming conventions, or code formatting.
Analyze a React/TypeScript component for compliance with coding guidelines and suggest improvements.
Simulates a Senior Engineer PR review to teach professional communication and industry naming standards. Use to prepare students for professional engineering environments and code review cultures.
Brutally honest code review in the style of Linus Torvalds, focusing on data structures, simplicity, and pragmatism. Use when you want critical, no-nonsense feedback that prioritizes engineering fundamentals over style preferences.
Create GitHub pull requests from code changes via API or generate PR content in chat. Use when user wants to create/open/submit PR, mentions pull request/PR/merge request/code review, or asks to show/generate/display/output PR content in chat (give me PR, PR to chat, send PR to chat, etc).
Generate production-ready REVIEW.md and AGENTS.md files for Devin Review's AI code review system. Use this skill whenever the user mentions Devin Review, REVIEW.md, Devin code review setup, PR review instructions for Devin, AI code review configuration for Devin, or wants to create instruction files that Devin's Bug Catcher uses. Also trigger when someone says "set up Devin review", "configure Devin for our repo", "create review rules for Devin", or asks about REVIEW.md / AGENTS.md — even if they don't say "Devin" explicitly but describe wanting AI-powered PR review instructions that work with Devin's auto-review or Bug Catcher.