Loading...
Loading...
Found 819 Skills
Documentation-driven development specification that requires Agent to consult official documentation and examples before generating code or fixing bugs, including API verification processes, search strategies and MCP invocation rules. It is applicable to scenarios such as accessing third-party libraries, troubleshooting API errors, and version changes.
A complete, opinionated development workflow skill for agents. Triggers when the user asks to implement a feature, fix a bug, or refactor code in a Git repo. Enforces hygiene, security, quality, and atomic commits.
Pull request and code review with diff-based routing across five dimensions: code quality and guideline compliance, test coverage analysis, silent failure detection, type design and invariant analysis, and comment quality auditing. Classifies changed files and loads only relevant review methodologies. Produces severity-ranked findings (Critical, Important, Suggestion) with confidence scoring. Replaces pr-review-toolkit plugin. Trigger phrases: "review my PR", "review this code", "check my changes", "is this ready to merge", "audit this PR", "review before committing", "check code quality", "any issues with this code", "pre-merge review", "look over my changes", "code review". Use this skill when reviewing code before commit or merge, checking PR quality, or when the user asks for feedback on recent modifications.
Receive and process code review feedback effectively. Applies suggestions, addresses comments, and iterates on implementation improvements.
Apply feedback and implement review suggestions. Incorporates reviewer comments into code changes systematically.
Request peer review with proper context and preparation. Structures review requests with clear description of changes and testing status.
Ensures tasks are genuinely resolved before marking them done. Activates at task checkpoints during plan execution — validates that fixes actually work, tests genuinely pass, and acceptance criteria are met. Prevents premature completion declarations.
Audits project physical structure: file hygiene, ignore file quality, framework convention compliance, domain/layer organization, naming conventions. Stack-adaptive via auto-detection.
Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design.
Prepare branch for code review by building context, identifying issues, and suggesting improvements
Review changes for test gaps, simplification, naming consistency, reuse opportunities, and TODO quality
Architecture optimization team skill. Analyzes codebase architecture, designs refactoring plans, implements changes, validates improvements, and reviews code quality via CSV wave pipeline with interactive review-fix cycles.