file-organization-standards
Enforces file naming conventions, directory structure, one class per file, Clean Architecture layer placement. Use when creating new files, organizing code, or refactoring file structure.
发现 tools code quality 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Enforces file naming conventions, directory structure, one class per file, Clean Architecture layer placement. Use when creating new files, organizing code, or refactoring file structure.
Use when preparing codebase for production commit, removing dead code, cleaning debug artifacts, auditing security, or performing pre-merge cleanup passes
Self-verification loop. Build/lint verification. Required before commit/PR. On failure, self-fix and re-verify.
Review C99 code for compliance with HBF's strict coding standards including compiler warnings, Linux kernel style, and licensing constraints. Use when reviewing or writing C code in this project.
Install pre-commit hooks to automatically lint markdown files before commits
Expert code review for Java/Spring Boot and TypeScript/Next.js codebases. Performs multi-dimensional reviews covering correctness, security, testability, architecture, and maintainability. Automatically delegat...
Rust conventions and reliability checklist for agents using cargo, clippy, and tests.
This skill should be used when the user needs help "fixing markdown issues", "repairing markdown lint errors", "resolving markdownlint violations", "MD001", "MD022", "MD024", "MD031", "MD042", "lint error", or...
Code quality enforcement with ESLint static analysis, VSCode workspace management, and automated code fixes. Supports JavaScript, TypeScript, React, Node.js with security and performance linting rules.
Handle code review feedback with technical rigor. Use this skill when receiving code review comments or feedback. Verify before implementing, ask before assuming, prioritize technical correctness over performat...
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, type...
Core coding standards, SOLID principles, Clean Code, and naming conventions. Use this skill for any coding task to ensure consistency.
Build quality standards, validation checkpoints, and compilation requirements
Comprehensive Python coding standards and style conventions for maintaining consistent, high-quality code across uv-managed Python projects
Guide for reviewing code quality, identifying issues, and suggesting improvements. Use when asked to review code, check for best practices, or conduct code reviews.
Python coding guidelines and best practices
Code comment style guidelines - when to comment and when not to
Perform systematic self-review of code changes before commits using structured checklist. Validates architecture boundaries, code quality, test coverage, documentation, and project-specific anti-patterns. Use b...
Validate and optimize CLAUDE.md files using Anthropic's best practices for focused sessions. Detects contradictions, redundancy, excessive length (200+ lines), emphasis overuse (2%+ density), broken links, and...
Use this skill when writing, editing, or reviewing Python code. Ensures code follows PEP 8 standards and Python best practices.
Review code for correctness, design quality, and complexity using principles from "A Philosophy of Software Design." Use this skill when reviewing pull requests, code changes, diffs, or when asked to find bugs,...
Validates that all imports follow fail-fast principle by detecting try/except ImportError patterns, conditional imports, and optional dependencies. Use before commits, when modifying imports, during code review...
Perform concise, high-quality code reviews focused on hygiene, simplicity, maintainability, documentation, correctness, performance, security, and robustness. Use when reviewing PRs/diffs/files to surface risks...
Safe-by-default git workflow and Conventional Commits. Triggers on git operations, reviewing diffs, staging files, creating commits, or branch changes. Prevents destructive operations without consent.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。