Code Review
Automated code review and analysis
pr-review-and-document
by marxbiotech
This skill should be used when the user asks to "review PR and save results", "run PR review with documentation", "create PR review document", "review and document PR", "save PR review to docs", "document PR review", or mentions reviewing a PR with the intention of saving the review results. Executes comprehensive PR review using pr-review-toolkit with opus model and posts results as a PR comment.
copilot-cli
by zhaoxuanZzz
Enable autonomous code development and collaboration using GitHub Copilot CLI. Use this skill when you need to write code, fix bugs, implement features, refactor code, create pull requests, or perform any development tasks autonomously with AI-powered assistance. Supports interactive and non-interactive modes, session management, automated PR workflows, and comprehensive code analysis. Ideal for automated development workflows, CI/CD integration, code reviews, and autonomous feature implementation.
pr-review-handler
by vijaykpatel
Handle PR review feedback by checking for comments, determining necessary changes, responding appropriately to reviewers, implementing fixes, and pushing updates. Use when the user asks to work on an existing open PR, address PR feedback, fix review comments, or handle bot review suggestions (Devin AI, Cursor Bugbot, etc.).
ask
by VitaDynamics
Ask a question about the codebase using parallel exploration agents
web-perf-ux
by october-academy
Web application performance and UX optimization through automated analysis. Use when developers need to (1) measure and diagnose performance issues using Lighthouse and Core Web Vitals, (2) identify root causes of LCP, CLS, INP problems, (3) analyze UX pain points like layout shifts or slow interactivity, (4) generate actionable improvement plans with concrete code-level fixes. Triggers on requests like "analyze performance", "why is my page slow", "fix CLS issues", "optimize web vitals", "run Lighthouse", "performance audit", or "improve page speed".
implement
by ianphil
This skill should be used when the user asks to "implement phase N", "implement task T001", "do TDD for phase", "implement T001-T009", or wants to execute tasks following strict TDD red-green-refactor workflow.
create-pr
by ruchernchong
Push branch and create GitHub pull request (auto-assigned)
specs
by petestewart
Create technical specifications from PRD.md and PROBLEM.md. Use when the user has a PRD and wants detailed technical specs for implementation. Also use when the user says "/specs", "create specs", "technical specifications", or "spec it out".
receiving-code-review
by feng501
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
prd
by AnsarUllahAnasZ360
Create self-verifying PRDs for autonomous execution. Interviews users to gather requirements, then generates structured prd.json with phased implementation and appropriate testing strategies. Supports 7 task categories with type-specific workflows. Use when user says "create a prd", "prd for", "plan a feature", "plan this", "write prd", or wants to plan any multi-step implementation work.
competitive-landscape
by TriNgo0108
This skill should be used when the user asks to "analyze competitors", "assess competitive landscape", "identify differentiation", "evaluate market positioning", "apply Porter's Five Forces", or requests competitive strategy analysis.
token-saver
by RubenAQuispe
"Token optimization dashboard with two sections - (1) Workspace file compression for ALL .md files in context, (2) AI model audit that detects current models and suggests cheaper alternatives. Shows \"possible savings\" until optimizations are applied. Triggers on \"optimize tokens\", \"reduce AI costs\", \"model audit\", \"save money on AI\"."
checking-breaking-changes-in-php-framework
by Seika139
"外部公開を想定したphpフレームワークのコードレビューをする際に、破壊的変更（breaking change）の有無を確認し、破壊的変更がある場合は適切に処理されているかをチェックするスキルです。"
exploring-data
by arielperez82
Exploratory data analysis using ydata-profiling. Use when users upload
github-pr-review-comments
by straub
Comprehensive workflow for managing GitHub PR review comments using gh CLI and GraphQL API. Use when asked to address review comments, find unreplied comments, reply to review threads, or resolve/unresolve review conversations. Supports finding ALL comments across pagination boundaries, replying to threads, and resolving conversations.
pix
by CoRLab-Tech
Launches an autonomous, pixel-perfect UI implementation loop using Figma MCP and Chrome.
obsidian-upgrade
by Cygnusfear
Upgrade Obsidian wikis to latest format. Handles structure migration (phases/tasks → features/specs), comment format upgrades (adding emoji prefixes), and Johnny Decimal feature organization. Use when user mentions "upgrade wiki", "migrate wiki", "update wiki format", or has old-format comments.
lg-desktop
by gyumaruya
"Docker virtual desktop with GUI automation. Use when asked to interact with desktop applications, automate GUI workflows, test UI, or operate software that requires a display. OCR-powered text inspection instead of screenshots (97% fewer tokens). Subcommands: up, down, status, update, inspect, click, type, key, screenshot, find-and-click, wait-for, assert, run, copy-from, copy-to."
reality-verification
by DUTSTECH
Detect fix vs add goals, diagnose failures before work, verify fixes after. Ensures "fix X" specs actually fix X.
using-git-worktrees
by ederheisler
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
spec-execute-plan
by nu1nux
Review an implementation plan and execute tasks in batches with checkpoints and reporting.
reviewing-code
by gajakannan
"Reviews code quality, architecture compliance, test adequacy, and acceptance criteria mapping. Activates when reviewing code, checking PRs, reviewing changes, assessing code cleanliness, or verifying acceptance criteria coverage. Does not handle security vulnerability scanning (security), writing production code (backend-developer or frontend-developer), or writing tests (quality-engineer)."
pr-to-origin-main
by atman-33
Create a pull request from current development branch to origin/main (not upstream/main). Use when you need to merge a feature branch into the main branch of your fork and want to ensure the PR targets origin/main with English descriptions. Always confirms remote target with user before creation to prevent accidentally creating PRs to upstream repositories.
gh-project-issue-loop
by mishankov
Continuously process available GitHub Project items by preparing project context once and then implementing linked issues in a loop via the gh-issue-to-pr skill. Use when asked to clear backlog from a GitHub Project board, batch-deliver project issues, or repeatedly pick and implement open project issues with gh CLI.