code-professionalization
Systematically transform codebase from 6.5/10 to 9/10 professional standards through testing, type safety, refactoring, and best practices
发现 content media code quality 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Systematically transform codebase from 6.5/10 to 9/10 professional standards through testing, type safety, refactoring, and best practices
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.
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
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.
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.
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
Automated code quality fixes for linting, types, unused variables, and error handling; use when fixing code quality issues in bulk
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...
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...
Fix linting and formatting issues automatically
TypeScript, lint, test, and build validation before committing
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...
Performs comprehensive code review with stack detection, deep logic tracing, and double-verification of bugs before reporting
Run comprehensive quality checks including Pint formatting, PHPStan analysis, and Pest tests. Use this before commits, after major changes, or when requested by user.
Review code quality, receive feedback with technical rigor, verify completion claims. Use before PRs, after implementing features, when claiming task completion, for subagent reviews.
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...
Code review framework and criteria. References security-sentinel for security checks. Use when performing code reviews or defining review 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...
系统化的代码审查方法,帮助发现问题并提供改进建议
Strict TypeScript rules. Use when writing ANY TypeScript.
Enforce RED-GREEN-REFACTOR cycle. Use when implementing features, fixing bugs, or writing any production code.
Request and process code reviews with proper context. Use after completing significant implementation work.
Markdownドキュメントの整合性と完全性をチェックする。 リンク切れ確認、アンカー検証、外部URL検証、空セクション検出を行い、 問題があれば修正案を提示する。 以下の依頼時に使用: - 「Markdownチェック」「ドキュメント...
Comprehensive code review methodology. 4 layers (Correctness, Security, Performance, Style), severity classification, 80% confidence threshold.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。