Loading...
Loading...
Found 1,194 Skills
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.
This skill should be used when the user asks to "review PR and save results", "run PR review with documentation", "create PR review document", "review and document PR", "save PR review to docs", "document PR review", or mentions reviewing a PR with the intention of saving the review results. Executes comprehensive PR review using pr-review-toolkit with opus model and posts results as a PR comment.
Full feature pipeline — pre-flight checks, TDD cycle, scope guard, quality commit. Combines pre-flight + tdd + scope-check + quality-commit into one flow. Use when implementing a feature, adding an endpoint, or building any non-trivial code change.
Rust code style and conventions for Syncpack. Use when writing or modifying Rust code. Covers functional patterns, imports, naming, and quality standards.
Deep code audit that finds dead wiring, silent failures, unfinished features, placeholder stubs, bloated files, and unnecessary complexity. Produces an actionable report with file:line references grouped by severity. Think of it as a senior dev doing a thorough PR review of the entire codebase. Triggers on: "code review", "audit the code", "review the code", "find dead code", "find placeholders", "check for stubs", "prune the code", "code cleanup", "implementation review", "completeness check", "find unused code".
TypeScript code style guide and formatting conventions. Use when writing TypeScript code, reviewing TypeScript files, refactoring .ts code, formatting TypeScript, or when working with TypeScript interfaces, classes, functions, or any .ts files. Apply these rules during code generation, code review, and when user mentions TypeScript style, formatting, conventions, semicolons, or code quality.
Use when fixing Rubocop violations. Runs Rubocop to identify issues, applies fixes following project conventions, and explains non-obvious corrections.
Review code for quality, security, and pattern compliance, then auto-fix Critical/High issues. Grounds every finding in actual codebase reference files.
Acts as a Principal Software Engineer to review completed or in-progress work against project standards, tech stack choices, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.
Initialize repo-scoped code review policy files under .opencode/review. Use when setting up project-specific review rules for /code-review.
Deep thinking mode - approach problems like a craftsman, obsess over details, and create elegant solutions
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation