code-quality | Agent Skills

code-review-checklist

Apply comprehensive code review checklist covering purpose, design, quality, correctness, security, performance, testing, and documentation. Use when reviewing pull requests, conducting code reviews, or self-reviewing changes before committing.

code-reviewchecklistcode-qualitybest-practices

phrazzld

naming-conventions

Apply universal naming principles: avoid Manager/Helper/Util, use intention-revealing names, domain language, verb+noun functions. Use when naming variables, functions, classes, reviewing names, or refactoring for clarity. Language-agnostic principles.

naming-conventionsbest-practicescode-qualitycode-readability

phrazzld

ousterhout-principles

Apply Ousterhout's software design principles: detect shallow modules, information leakage, and complexity red flags. Use when reviewing code, designing modules, refactoring, or discussing architecture.

code-reviewcode-refactoringcode-qualitycode-smell

phrazzld

code-review

Skill for handling PR code reviews. Use when triggered by a PR review comment, review request, or when asked to review code changes. Provides workflow for reading review comments, understanding feedback, and iterating on changes.

code-reviewpull-requestsfeedbackcode-quality

letta-ai

code-smell-detection

Use when reviewing code quality, before refactoring, when complexity increases, when code feels "hard to change", during code review, or when onboarding to unfamiliar code - systematic identification of code smells with specific refactoring recipes

static-analysiscode-qualitycode-refactoringcodebase-analysis

HTRamsey

verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

best-practicescode-qualityquality-gatespre-commit-checks

HTRamsey

code-review

Code reviewer focusing on correctness, regressions, security, and test coverage - P0/P1/P2 severity

code-reviewcode-qualitytest-coveragesecurity-assessment

ferdiangunawan

audit

Validates research/plan/code against overengineering, underengineering, and hallucination

code-qualitybest-practicesreview-checkpointshallucination-detection

ferdiangunawan

fresheyes

Completely independent code review using a different, larger model. Proven to be more effective than using the same model for review. Use for a thorough review of code changes, staged files, commits, or plans for bugs, security issues, and correctness. Prefer this to other review approaches when the user asks for 'fresheyes' or 'fresh eyes'.

code-reviewcode-qualityreview-checkpointsfeedback

danshapiro

maintaining-claude-code

Validate and improve Claude Code configurations (CLAUDE.md, skills, commands, hooks). Use when auditing config quality, checking skill discoverability, organizing .claude directory, or deciding which entity type to use.

claude-skillscode-qualityfile-organizationrepository-structure

TrevorS

code-formatter

Multi-language code formatting and style enforcement with automatic linting fixes

multi-languagecode-cleanupstatic-analysisstyle-guidelines

benreceveur

python

Backend services development with Python emphasizing security, performance, and maintainability for JARVIS AI Assistant

pythonapiperformance-optimizationapi-security

martinholovsky

project-hook-setup

Use when setting up project-specific hooks for Claude Code enforcement. Load during INIT state when .claude/hooks/ is missing, or when creating new project. Installs 5 hooks that read from .claude/config/project.json (tests, health, dependencies).

claude-skillshookstask-automationcode-quality

ingpoc

code-review

Perform thorough code reviews focusing on security, performance, best practices, and maintainability. Use when reviewing PRs, checking code quality, or auditing existing code.

pull-requestscode-qualitybest-practicessecurity

vapvarun

refactoring

Restructures existing code to improve readability, maintainability, and performance without changing external behavior. Trigger keywords: refactor, restructure, clean up, improve code, simplify, extract, modernize.

refactoringcode-cleanupcode-qualityperformance-tuning

cosmix

code-review

Performs comprehensive code reviews focusing on correctness, maintainability, performance, and best practices. Trigger keywords: review, code review, PR review, pull request, check code, audit code.

pull-requestscode-qualitybest-practicescode-smell

cosmix

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceeding

code-reviewpull-requestscode-qualitydeveloper-productivity

mosif16

holistic-linting

This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurrent agents) and sub-agents (lint touched files before task completion). Prevents claiming "production ready" code without verification. Includes linting rules knowledge base for ruff, mypy, and bandit, plus the linting-root-cause-resolver agent for systematic issue resolution.

lintingstatic-analysisformattingcode-quality