GitHub
nix-cleanup
Run janitorial cleanup for this flake: flake check, statix/deadnix linting, and safe hygiene fixes.
Skills IA tools code quality
Découvrez les skills tools code quality, comparez leurs dépôts et consultez leurs instructions.
Catégories: tools code quality
tools code quality Effacer les filtres
Explorer
GitHub
tailwind-style-guidelines
Enforces consistent Tailwind CSS usage, preventing utility abuse and visual inconsistency.
GitHub
lang-ts
TypeScript/JavaScript conventions and reliability checklist for agents (build, typecheck, tests).
GitHub
receiving-code-review
当收到代码审查反馈时使用，在实施建议之前，特别是如果反馈似乎不清楚或技术上可疑时 - 需要技术严谨性和验证，而不是表演性同意或盲目实施
GitHub
run
Run the current project based on detected language
GitHub
typescript-configuration
TypeScript configuration standards and tsconfig.json patterns
GitHub
code-review
Code review checklist for changes made by an agent.
GitHub
safe-editing
Best practices for making safe, verified code edits
GitHub
architecting-structure
Enforces "Feature-First" architecture across standard frameworks. Use to scaffold new projects, refactor messy ones, or enforce clean file organization rules.
GitHub
code-review-assist
コード品質チェックと改善提案。Lintエラー修正、未使用コード削除、リファクタリング時に使用。警告、unused、refactor時に使用。
GitHub
quality-detect-refactor-markers
Finds all REFACTOR markers in codebase, validates associated ADRs exist, identifies stale markers (30+ days old), and detects orphaned markers (no ADR). Use during status checks, before feature completion, or f...
GitHub
coding-best-practices
General coding principles for writing clean, maintainable code. Triggers on any development work, code reviews, refactoring, or when adding dependencies. For frontend/React code, also apply web-ui-best-practice...
GitHub
role-reviewer
Activate Code Reviewer mode for code review and quality assurance. Use when reviewing code for bugs, security issues, or optimization opportunities.
GitHub
coding-conventions
Provides coding style rules for Python and PowerShell. Apply when writing, editing, reviewing, or debugging code.
GitHub
code-reviewer
コード品質の専門家。品質・セキュリティ・パフォーマンスの観点からコードをレビュー。使用場面: (1) コードレビュー、(2) バグ発見、(3) パフォーマンス改善提案、(4) セキュリティ脆弱性チェック、(5) ベストプラクティス適...
GitHub
frontend-code-review
Perform comprehensive frontend code reviews for JavaScript, TypeScript, React, Vue, Angular, and other frontend frameworks. Use this skill when reviewing pull requests, auditing existing codebases, or providing...
GitHub
dendritic-validate
Validate dendritic Nix pattern usage and flag deviations.
GitHub
spots-philosophy-integration
Ensures all code aligns with SPOTS core philosophy: "Doors, not badges", meaningful connections, real-world enhancement. Use when implementing features, reviewing code, or making architectural decisions to vali...
GitHub
minimal-abstractions
Enforces the principle of avoiding unnecessary abstractions and complexity in codebases. Use when evaluating new abstractions, reviewing architecture proposals, detecting over-engineering, or simplifying existi...
GitHub
pragmatic-audit
Scan codebase for Pragmatic Programmer anti-patterns. Reports findings. Triggers on "pragmatic audit" or "/pragmatic-audit".
GitHub
python-best-practices-type-safety
Systematic resolution of pyright/mypy type errors with categorization and fix templates. Use when pyright fails, type errors are reported, adding type annotations, or enforcing type safety. Analyzes Python type...
GitHub
code-quality
Non-negotiable code quality standards for structure, testing, naming, and documentation
GitHub
util-multi-file-refactor
Optimizes multi-file refactoring workflows by enforcing token-efficient MultiEdit usage (30-50% savings), coordinating changes across files, validating imports/references, and running quality gates. Use when re...
GitHub
lint-and-validate
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...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.