Loading...
Loading...
Found 815 Skills
Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Git commit with enforced quality gates, proper message format, and safe push workflow
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Remove AI-generated code slop from the current branch. Use after writing code to clean up unnecessary comments, defensive checks, and inconsistent style.
Analyze code complexity, cyclomatic complexity, maintainability index, and code churn using metrics tools. Use when assessing code quality, identifying refactoring candidates, or monitoring technical debt.
Provide structured code review guidance for catching defects and improving quality. This skill should be used when the user asks to 'review this code', 'check for issues', 'PR review', 'code quality check', or wants systematic code evaluation. Keywords: code review, PR, pull request, quality, defects, security, maintainability, performance.
Phase 2 of the feature workflow —— Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and go back to discuss the plan instead of pushing forward blindly.
Follow this sub-process when fixing bugs — turn the verbal description of "problem found" into a closed loop from verification to repair, leaving three documents: problem report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code" to avoid common pitfalls: the problem description in your mind disappears after the fix, you only fix the surface without analyzing the root cause, the scope of repair expands and cannot be traced, and you don't know if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing artifacts. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only retaining the fix-note.
Use when reviewing pull requests, conducting code quality audits, or identifying security vulnerabilities. Invoke for PR reviews, code quality checks, refactoring suggestions.
SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. Use when reviewing architecture, checking code quality, refactoring, or discussing design decisions. Triggers on "review architecture", "check code quality", "SOLID principles", "design patterns", or "clean code".
Python linting with Ruff - an extremely fast linter written in Rust. Use when: (1) Standardizing code quality, (2) Fixing style warnings, (3) Enforcing rules in CI, (4) Replacing flake8/isort/pyupgrade/autoflake, (5) Configuring lint rules and suppressions.
Python type checking expertise using ty - the extremely fast type checker by Astral. Use when: (1) Adding type annotations to Python code, (2) Fixing type errors reported by ty, (3) Migrating from mypy/pyright to ty, (4) Configuring ty for projects, (5) Understanding advanced type patterns (generics, protocols, intersection types), (6) Setting up ty in editors (VS Code, Cursor, Neovim, PyCharm).