Total 44,046 skills, Code Quality has 2066 skills
Showing 12 of 2066 skills
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.
Guidance on Python code style optimization and Pythonic idioms; Based on the complete content of *One Python Craftsman* and the "Friendly Python" concept, covering variable naming, control flow, data types, container types, function design, exception handling, decorators, file operations, and SOLID principles; Providing user-friendly and maintainer-friendly design patterns, review checklists, and over 140 practical templates
Prioritizes the use of new features available in Python 3.12 and later versions.
Systematic code review for Java with null safety, exception handling, concurrency, and performance checks. Use when user says "review code", "check this PR", "code review", or before merging changes.
This skill is used when users request phrases such as 'handle PR review issues', 'fix review items', 'resolve PR feedback', 'process review issues one by one', 'complete review tasks', 'run pr review resolver', 'resolve PR review', 'address review comments', 'fix review findings', or 'handle code review'. It reads the review comments of the PR associated with the current branch, discusses each unresolved issue with the user one by one, lets the user decide on the handling approach, and executes fixes in parallel as background subtasks.
Discourse 패턴으로 다관점 리뷰를 수행한다. Tech Spec 리뷰와 에픽 통합 코드 리뷰를 모두 처리하며, 쟁점 해소 프로토콜에 따라 합의/미합의를 분리한다.
스프린트 중 코드 리뷰에서 발견된 반복 패턴을 conventions.md에 반영한다. Convention Guard의 규칙 소스를 축적하여 다음 스프린트의 리뷰 품질을 높인다.
Fork-based PR implementation with isolation check. Runs isolation check before starting work. Triggers: "implement PR", "implement contribution", "fork implementation", "code the PR".
PR-specific validation: isolation, upstream alignment, quality, scope creep. Triggers: "validate PR", "pr validation", "check PR scope", "scope creep check", "isolation check".
Analyzes code modules and generates structured technical reports with architecture diagrams. Trigger: When the user asks to analyze, explain, or document a module, file, or codebase section.
Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.
Run parallel quality reviews (React, SOLID, Security, Simplification, Slop) on branch changes and auto-fix issues