Loading...
Loading...
Found 1,227 Skills
Local Code Review - analyzes code changes and provides structured feedback before commit
Auto-selects best Kaizen method (Gemba Walk, Value Stream, or Muda) for target
Reflect on previus response and output, based on Self-refinement framework for iterative improvement with complexity triage and verification
This skill should be used when the user requests actions such as 'review code', 'do a code review', 'review my branch', 'review MR !1234', or 'review PR'
Diff Review - analyzes code changes and provides structured feedback before commit
Reviews code for project standards compliance and finds duplicates. Use when - reviewing code quality, checking standards, finding duplicates, analyzing compliance. Trigger keywords - standards review, check standards, find duplicates, code review, compliance check, reusable code.
Run agentlint CLI after code changes to catch patterns for AI evaluation. Activate when finishing code modifications, before committing, or when the developer asks to lint, scan, or review code with agentlint. Covers agentlint check, agentlint list, agentlint review, agentlint init, inline suppression, and output interpretation.
Classify a code quality concern into the right enforcement tool and act on it. Activate when the user wants to enforce a pattern, catch a mistake, add a check, create a rule, prevent a practice, guard against regressions, set up linting, improve their feedback loop, or asks "how do I make sure X."
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Review code changes for correctness, security, and maintainability. Supports local git diffs (staged or working tree) and remote Pull Requests (by ID or URL). Use when the user asks to review code, check a PR, audit changes, or wants feedback on code quality before merging.
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 when implementing any feature or bugfix, before writing implementation code