Loading...
Loading...
Found 1,194 Skills
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.
Explicit anti-rationalization enforcement for maximum-rigor task execution. Loads all anti-rationalization patterns, gate enforcement, and pressure resistance as a composable modifier on any task. Use when executing critical production changes, security-sensitive code, complex multi-file refactors, or any task where shortcuts could cause harm. Use for "with rigor", "carefully", "maximum verification", or "no shortcuts". Do NOT use for trivial lookups, documentation-only edits, or simple typo fixes where full gate enforcement would be disproportionate overhead.
Run Go quality checks via make check with intelligent error categorization and actionable fix suggestions. Use when user requests "run quality checks", "check PR quality", "verify code quality", or "run make check". Use before creating commits or during PR review. Do NOT use for non-Go repositories, repositories without a Makefile, or manual linter invocation.
Multi-language code quality gate with auto-detection and language-specific linters. Use when user asks to "run quality checks", "quality gate", "lint all", "check everything", "pre-commit checks", or "is this code ready to commit". Use for verifying code quality across polyglot repos. Do NOT use for single-language linting (use code-linting) or comprehensive code review (use systematic-code-review).
Must be followed when writing error handling code that includes try-catch. Ensure that the catch block has substantial processing logic, is not empty, does not only log information, and must handle or re-throw exceptions. Trigger keywords: try-catch specification, error handling best practices, exception handling review.
Analyzes Rails code quality, architecture, and patterns without modifying code. Use when the user wants a code review, quality analysis, architecture audit, or when user mentions review, audit, code quality, anti-patterns, or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist agents), writing new tests (use rspec-agent), or generating new features.
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
Run Codex code review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
Generate a comprehensive Sentry bug report. Use when the user explicitly asks to "generate a bug report".
LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".
Audit a codebase for handcrafted code that duplicates functionality already available in the project's dependencies. Reads package.json, launches parallel exploration agents, verifies replacement feasibility, and produces a structured refactor plan. Audit only -- does not execute changes.
Agent skill for refinement - invoke with $agent-refinement