Total 54,172 skills, Code Quality has 2444 skills
Showing 12 of 2444 skills
Apply feedback and implement review suggestions. Incorporates reviewer comments into code changes systematically.
Writes Kani bounded model checker proofs for Rust programs. Proves conservation, isolation, arithmetic safety, and access control properties. Use when the user asks to write formal verification, Kani proofs, model checking, or when code contains kani::,
Interactively fix any type checking issues in Python code
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.
JaCoCo Java code coverage tool USE WHEN: user mentions "JaCoCo", "Java coverage", "code coverage", asks about "coverage threshold", "jacoco-maven-plugin", "coverage report", "LINE coverage", "BRANCH coverage" DO NOT USE FOR: JavaScript/TypeScript coverage - use Vitest skill, SonarQube analysis - use `sonarqube` skill, test execution - use testing skills
Code specialist for writing, debugging, and technical implementation. Use when the user needs code written, bugs fixed, files edited, or features built.
Applicable to code-centric tasks such as coding, debug/debugging, bug fixing, refactor/refactoring, code review, scripting, automation, and implementation planning.
Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex".
Validate-then-fix workflow for PR review comments: Fetch, Validate, Plan, Fix, Commit. Use when user wants to address PR feedback, fix review comments, or resolve reviewer requests. Use for "fix PR comments", "address review", "pr-fix", or "resolve feedback". Do NOT use for creating PRs, reviewing code without fixing, or general debugging unrelated to PR comments.
Coordinate PR mining to extract tribal knowledge and coding standards from GitHub PR history. Use when mining review comments, extracting coding rules, tracking mining jobs, or analyzing reviewer patterns across repositories. Use for "mine PRs", "extract standards", "coding rules from reviews", or "reviewer patterns". Do NOT use for code review, linting, static analysis, or writing new coding standards from scratch without PR data.
Code quality and deviation gate between /implement and /test. Reads the task document and changed files, validates coding standards, classifies deviations (minor/medium/major), and decides whether implementation is ready for testing. Runs automatically in the auto-chain between implement and test. Also invoke manually after any implementation to catch issues before wasting a test run.