GitHub
code-professionalization
Systematically transform codebase from 6.5/10 to 9/10 professional standards through testing, type safety, refactoring, and best practices
Skills IA content media code quality
Découvrez les skills content media code quality, comparez leurs dépôts et consultez leurs instructions.
Catégories: content media code quality
content media code quality Effacer les filtres
Explorer
GitHub
norminette-checker
Check and fix C code according to 42 School's Norminette standards. Use when checking code style, before committing, or when user mentions norm/norminette.
GitHub
pr-creator
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
GitHub
review
This skill should be used when the user asks to "review code", "check for bugs", "audit this file", or wants feedback on code quality, security, and best practices.
GitHub
code-review
Performs structured code reviews focusing on bugs, security, performance, and best practices. Use when reviewing code, pull requests, diffs, or when the user asks for feedback on implementations.
GitHub
code-review-preferences
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
GitHub
code-quality-tools
Automated code quality fixes for linting, types, unused variables, and error handling; use when fixing code quality issues in bulk
GitHub
radflow-compliance
Audit and fix AI-generated or existing code for RadOS design compliance. Use after generating UI code or when reviewing PRs. Catches common mistakes like wrong shadows, hardcoded colors, missing components, and...
GitHub
typescript-strict-guard
Use when writing or reviewing TypeScript code. Enforces strict mode standards, explicit typing, and best practices. Prevents 'any' types, @ts-ignore comments, and non-null assertions. This is a COMPREHENSIVE sk...
GitHub
lint-fix
Fix linting and formatting issues automatically
GitHub
feedback-loops
TypeScript, lint, test, and build validation before committing
GitHub
biome-to-oxc
Migrate JavaScript/TypeScript projects from Biome to oxlint + oxfmt with Prettier fallback. Use when user asks to "migrate to oxlint", "switch from biome to oxc", "use oxfmt", or wants to adopt the oxc toolchai...
GitHub
review
Performs comprehensive code review with stack detection, deep logic tracing, and double-verification of bugs before reporting
GitHub
laravel-quality
Run comprehensive quality checks including Pint formatting, PHPStan analysis, and Pest tests. Use this before commits, after major changes, or when requested by user.
GitHub
code-review
Review code quality, receive feedback with technical rigor, verify completion claims. Use before PRs, after implementing features, when claiming task completion, for subagent reviews.
GitHub
nodejs-subpath-imports
Use when debugging subpath import errors (ERR_PACKAGE_IMPORT_NOT_DEFINED, "only allows ./"), configuring package.json imports field, migrating from tsconfig paths, or building cross-platform code with condition...
GitHub
code-review-standards
Code review framework and criteria. References security-sentinel for security checks. Use when performing code reviews or defining review standards.
GitHub
enforcing-typescript-standards
Enforces the project's core TypeScript standards including explicit typing, import organization, class member ordering, and code safety rules. ALWAYS apply when creating, modifying, or reviewing any TypeScript...
GitHub
code-review
系统化的代码审查方法，帮助发现问题并提供改进建议
GitHub
typescript-strict
Strict TypeScript rules. Use when writing ANY TypeScript.
GitHub
test-driven-development
Enforce RED-GREEN-REFACTOR cycle. Use when implementing features, fixing bugs, or writing any production code.
GitHub
requesting-code-review
Request and process code reviews with proper context. Use after completing significant implementation work.
GitHub
markdown-check
Markdownドキュメントの整合性と完全性をチェックする。 リンク切れ確認、アンカー検証、外部URL検証、空セクション検出を行い、 問題があれば修正案を提示する。 以下の依頼時に使用: - 「Markdownチェック」「ドキュメント...
GitHub
code-review
Comprehensive code review methodology. 4 layers (Correctness, Security, Performance, Style), severity classification, 80% confidence threshold.
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é.