Total 44,144 skills, Code Quality has 2071 skills
Showing 12 of 2071 skills
Refactor MoonBit code to be idiomatic: shrink public APIs, convert functions to methods, use pattern matching with views, add loop invariants, and ensure test coverage without regressions. Use when updating MoonBit packages or refactoring MoonBit APIs, modules, or tests.
Diff Review - analyzes code changes and provides structured feedback before commit
Structured code review approach covering security, quality, performance, and consistency.
Bence's code style, tech stack, and workflow conventions
Review code for conceptual errors, wrong assumptions, edge cases, and overcomplication; use after medium/large changes or when risk is high.
Use this skill when validating ANY potential code review finding. Apply BEFORE classifying to verify the finding is real; can you trace incorrect behavior, is it handled elsewhere, and are you certain about framework semantics? If any answer is no, DO NOT create the finding.
Automate lifecycle checks for migration code (TODO(migration)). Detect expired or insufficiently documented migration code and output results in report format. It is used for checking remaining TODO(migration) entries in the codebase, cleaning up expired migration code, and taking inventory of technical debt. This is a mechanism to prevent leaving "to be deleted later" code unattended.
Deep line-by-line code review that finds all bugs, logic errors, redundancies, and issues. Traces call stacks, fixes everything, verifies 100%. Use when reviewing features, PRs, code changes, or auditing for bugs.
Scope-aware GitHub PR review with user-friendly tone and trust tier validation
Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs, validating fixes, or conducting root cause analysis. Elementary approach to finding truth through systematic observation.
Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.
Use when a request asks for software design patterns or design principles, including explanations, comparisons, summaries, or quick reference grounded in local docs.