Loading...
Loading...
Found 817 Skills
Apply feedback and implement review suggestions. Incorporates reviewer comments into code changes systematically.
Request peer review with proper context and preparation. Structures review requests with clear description of changes and testing status.
Use before claiming work is done, fixed, or passing — requires running verification commands and confirming output before any success claim. Prevents false completion claims, unverified assertions, and "should work" statements.
Post-implementation reality check. Run after tests pass, before declaring done. Use when completing a feature, bug fix, refactor, or integration — or when asked to verify, sanity check, or confirm something actually works.
Audits project physical structure: file hygiene, ignore file quality, framework convention compliance, domain/layer organization, naming conventions. Stack-adaptive via auto-detection.
SOLID principles for object-oriented design — Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Covers motivation, violations, fixes, and multi-language examples (PHP, Java, Python, TypeScript, C++) for building maintainable, extensible software.
Use when writing similar code in multiple places. Use when copy-pasting code. Use when making the same change in multiple locations.
Coding conventions enforcement agent. Auto-invoked when writing new code, reviewing code quality, adding headers, or checking documentation compliance across Python, TypeScript/JavaScript, and C#/.NET.
Perform structured code review and kanban transitions for completed task
This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.
Use this skill for multi-model AI code review. Trigger whenever the user asks to review code changes, audit a diff, check code quality, review a PR, review commits, or review uncommitted changes before pushing or merging. Also trigger when they say 'code review', 'review my changes', 'check this before I merge', or want multiple perspectives on code. Runs Codex and Claude reviews in parallel, then synthesizes a unified report. Do NOT use for reviewing documentation, markdown, or non-code files, or for trivial single-line changes.
Architect/CR agent role. Receives git diff, task spec, ADRs, design doc, and project conventions. Reviews code and returns APPROVED or CHANGES_REQUIRED. Do NOT invoke directly — dispatched by team-execute.