makepad-code-quality
Makepad-aware code simplification and quality improvement. Understands Makepad-specific patterns that must NOT be simplified, such as borrow checker workarounds, grapheme handling, live_design! syntax, and widget lifecycle patterns. Use when refactoring or reviewing Makepad code.
pr-review-standards
Code quality standards for PR review agents including try/except rules, logging patterns, type hints, and verification requirements. Use when reviewing code, spawning PR review agents, or validating code quality.
Python Style Standards
Python coding standards including line length (80 chars), naming conventions (snake_case, PascalCase), type hints, docstrings, exception handling, and logging patterns. Use when writing new Python code or reviewing code quality.
code-review-patterns
Code review best practices including review checklists (functionality, tests, documentation, security, performance), providing constructive feedback, automated checks integration, and handling review comments. Use when reviewing pull requests, providing code feedback, responding to review comments, or setting up review processes.
programming
Always use this skill when writing or editing code of any sort!
dev-review
REQUIRED Phase 6 of /dev workflow. Combines spec compliance and code quality checks with confidence scoring.
dev-delegate
Internal skill used by dev-implement during Phase 5 of /dev workflow. NOT user-facing - should only be invoked by dev-ralph-loop inside each implementation iteration. Handles Task agent spawning with TDD enforcement and two-stage review (spec compliance + code quality).
code-reviewer
코드 리뷰, 코드리뷰, 리뷰, PR 리뷰, 검토 - Expert at reviewing code for quality, adherence to architectural principles, security, and performance. Use this to ensure code meets project standards before merging or after implementation.
next-silent-failure-hunter
Identify silent failures, inadequate error handling, and inappropriate fallback behavior. Use when reviewing code with error handling, catch blocks, or fallback logic.
next-type-design-analyzer
Analyze type design quality and invariants. Use when introducing new types, during PR creation with data models, or when refactoring type designs.
next-code-reviewer
Review code for adherence to project guidelines, style guides, and best practices. Use after writing or modifying code, before committing changes or creating pull requests.
next-code-simplifier
Simplify code for clarity, consistency, and maintainability while preserving all functionality. Use after completing a coding task or after passing code review to polish the implementation.
style-guide-adherence
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
review-gate
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met
no-deferred-work
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
code-reviewer
Use when explicitly asked to run the code-reviewer subagent or when another skill requires the code-reviewer agent card.
clean-commits
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Page 1 of 9 · 159 results