Total 50,277 skills, Code Quality has 2282 skills
Showing 12 of 2282 skills
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."
Review a spec or concrete code changes and report evidence-backed bugs, regressions, and risks.
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 about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
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 encountering any bug, test failure, or unexpected behavior, before proposing fixes
Investigate Problem - analyzes a problem in the codebase and proposes actionable solutions
Use when writing Move code on Sui to ensure 2024 edition syntax is used. Applies to method calls, string literals, vector operations, option handling, loops, and struct unpacking. Use whenever writing Move code to avoid legacy function-call syntax patterns.
Write meaningful documentation that explains why not what; focus on complex business logic and self-documenting code