Loading...
Loading...
Found 753 Skills
Use when implementing well-scoped Python tasks with clear requirements, writing unit tests, and producing documented code for senior-developer review.
Manage Azure Repos including branches, pull requests, and code reviews. Use when working with Azure Repos or managing repository operations.
Build verification, error recovery, and application of review fixes. Use this when the user mentions build verification, error recovery, applying review fixes, test failures, lint errors, or CI breaks. Do NOT load this for: implementation work, reviews, setup, or new feature development.
Vibe Kanban orchestration platform for AI coding agents: workspaces, sessions, task management, code review, git worktrees, multi-agent support. Keywords: Vibe Kanban, AI agents, Claude Code, Codex, Gemini, kanban board, git worktree, code review, MCP server, workspaces, sessions.
Use when wanting independent review from external models before merging, committing, or finalizing architecture or plan decisions, or when the user asks for a second opinion, codex review, or gemini review
Use when writing any code - enforces clean architecture with descriptive names, real implementations, no backward compatibility concerns, and no lint suppressions
Respond to PR review comments with critical evaluation. Use when addressing code review feedback, responding to bot review comments (Gemini Code Assist, CodeRabbit, etc.), or handling PR suggestions. Fetches comments, evaluates each against project context, applies valid fixes, declines invalid suggestions with reasoning, and posts responses.
Guidance for writing, reviewing, and debugging Unreal Editor for Fortnite (UEFN) Verse code using Epic's official language documentation. Use when implementing Verse devices, classes, functions, control flow, containers, failure contexts, specifiers/attributes, modules/imports, effects, concurrency, or translating logic into valid Verse.
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
Use this skill when posting the final summary comment after all inline comments are posted. Apply as the LAST step of code review after all findings are classified and inline comments are complete. Detects context (GitHub sticky comment, new comment, or local file) and routes output accordingly.
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
Orchestrate full development workflow. Use when implementing features, starting structured development, or user mentions "workflow" or "implement issues".