home/categories/code-quality
category focus

Code Quality

Linters, formatters, and static analysis.

2681 个技能all categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
450

blog-seo-check

Post-writing SEO validation with pass/fail checklist covering title tag length and keyword placement, meta description quality, heading hierarchy and keyword density, internal/external link audit with anchor text analysis, canonical URL verification, Open Graph meta tags (og:title, og:description, og:image), Twitter Card validation, URL structure optimization, and image alt text presence. Produces prioritized fix list with specific recommendations. Use when user says "seo check", "check seo", "validate seo", "blog seo", "seo validation", "on-page seo", "title tag check", "meta description check", "heading check", "link audit".

AgriciDaniel
AgriciDaniel
testing-security
open
code-quality
449

example

MUST load before creating or modifying any AG Charts, AG Grid, or AG Studio code example — whether for gallery, docs, or Plunker. Contains required conventions that differ from training data. Also load when troubleshooting example issues (TypeScript errors, rendering problems) or asking about example file structure and patterns.

ag-grid
ag-grid
testing-security
open
code-quality
449

validate-prompts

Validate prompt file references for consistency, canonical paths, and hygiene

ag-grid
ag-grid
testing-security
open
code-quality
448

gum-tool-variable-references

Reference guide for Gum's variable reference system — Excel-like cross-instance/cross-element variable binding using Roslyn-parsed assignment syntax. Load this when working on VariableReferenceLogic, EvaluatedSyntax, ApplyVariableReferences, VariableChangedThroughReference, or the VariableReferences VariableListSave.

vchelaru
vchelaru
testing-security
open
code-quality
448

validate-code-changes

Validate all code changes on the current branch. Spawns QA and refactoring agents in parallel to review for correctness, edge cases, code quality, and pattern adherence. Use when ready to review branch changes before merging.

vchelaru
vchelaru
testing-security
open
code-quality
443

typescript

TypeScript anti-slop guardrails. Use when writing or reviewing .ts, .tsx, and .mts files. Covers patterns that Biome, tsc, and rslint do not catch.

web-infra-dev
web-infra-dev
testing-security
open
code-quality
440

humanize-rlcr

Start RLCR (Ralph-Loop with Codex Review) with hook-equivalent enforcement from skill mode by reusing the existing stop-hook logic.

humania-org
humania-org
testing-security
open
code-quality
439

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

ErlichLiu
ErlichLiu
testing-security
open
code-quality
432

eval-quality-workflow

Fix or review a single evaluation against all EVALUATION_CHECKLIST.md standards. Use "fix" mode to refactor an eval into compliance, or "review" mode to assess compliance without making changes. Use when user asks to fix, review, or check an evaluation's quality. Trigger when the user asks you to run the "Fix An Evaluation" or "Review An Evaluation" workflow. Do NOT use for reviewing ALL evals against a single code quality standard (use code-quality-review-all instead).

UKGovernmentBEIS
UKGovernmentBEIS
testing-security
open
code-quality
432

eval-validity-review

Review a single evaluation's validity — whether its claims hold up, whether its name is accurate, whether samples can be both succeeded and failed at, and whether scoring measures ground truth. Use when user asks to check validity of an eval, or as part of the Master Checklist workflow. Do NOT use for code quality or test coverage (use eval-quality-workflow or ensure-test-coverage instead).

UKGovernmentBEIS
UKGovernmentBEIS
testing-security
open
code-quality
430

electrobun-rpc

Use when working with Electrobun's RPC system — defineElectrobunRPC, Electroview.defineRPC, ElectrobunRPCSchema types, bun-to-renderer and renderer-to-bun communication. Activates automatically when RPC code is present.

milady-ai
milady-ai
testing-security
open
code-quality
430

electrobun-core

Use when working on any Electrobun desktop app — BrowserWindow, BrowserView, events, app lifecycle, ApplicationMenu, Tray, and electrobun.config.ts. Activates automatically when editing Electrobun project files.

milady-ai
milady-ai
testing-security
open
code-quality
388

python-standards

Apply Python tooling standards including uv package management, pytest testing, ruff/basedpyright code quality, one-line docstrings, and self-documenting code practices. Use this skill when working with Python backend code, managing dependencies, running tests, or ensuring code quality. Apply when installing packages, writing tests, formatting code, type checking, adding docstrings, organizing imports, or deciding whether to create new files vs. extending existing ones. Use for any Python development task requiring adherence to tooling standards and best practices.

maxritter
maxritter
testing-security
open
code-quality
388

css-standards

Write consistent, maintainable CSS following the project's methodology (Tailwind, BEM, utility classes, CSS modules) with design system adherence and performance optimization. Use this skill when writing or modifying styles, CSS files, utility classes, CSS-in-JS, styled components, or any styling code. Apply when working with .css, .scss, .module.css files, Tailwind utility classes, styled-components, CSS modules, design tokens (colors, spacing, typography), framework-specific styling approaches, optimizing CSS for production, implementing CSS purging or tree-shaking, or avoiding style overrides. Use for any task involving visual styling, layout styling, design system implementation, or CSS organization.

maxritter
maxritter
testing-security
open
code-quality
378

validate-openapi-spec

Use when checking if an OpenAPI spec is valid, looking for errors, or running `speakeasy lint`

speakeasy-api
speakeasy-api
testing-security
open
code-quality
376

code-consistency-logging-standards

Check Python logging levels and patterns for correctness. Focus on identifying wrong severity levels and missing exception handling. Use when reviewing code quality.

taylorsatula
taylorsatula
testing-security
open
code-quality
376

investigate-dependencies

Conduct thorough dependency audits to identify redundant code, unused features, and improper usage patterns. Examines each import to ensure we're leveraging existing capabilities rather than reinventing functionality.

taylorsatula
taylorsatula
testing-security
open
code-quality
305

error-messages

Error Message Style Guide for Validation Errors

githubnext
githubnext
testing-security
open
code-quality
303

writing-nix

Writes idiomatic, performant, and maintainable Nix code. Covers best practices, anti-patterns to avoid (like `with`), module system design, and performance optimization.

khaneliman
khaneliman
testing-security
open
code-quality
303

code-review

Conduct thorough, actionable code reviews focusing on critical issues. Use when reviewing pull requests, analyzing code changes, identifying bugs, security vulnerabilities, or suggesting improvements that developers will actually implement.

khaneliman
khaneliman
testing-security
open
code-quality
303

validating-nix

Validates Nix code correctness, syntax, and buildability. Use when checking for errors, debugging build failures, formatting code, or verifying flake outputs.

khaneliman
khaneliman
testing-security
open
code-quality
256

coding-guidelines

Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名

ZhangHanDong
ZhangHanDong
testing-security
open
code-quality
256

m15-anti-pattern

Use when reviewing code for anti-patterns. Keywords: anti-pattern, common mistake, pitfall, code smell, bad practice, code review, is this an anti-pattern, better way to do this, common mistake to avoid, why is this bad, idiomatic way, beginner mistake, fighting borrow checker, clone everywhere, unwrap in production, should I refactor, 反模式, 常见错误, 代码异味, 最佳实践, 地道写法

ZhangHanDong
ZhangHanDong
testing-security
open
code-quality
212

quality-guardian

运行和分析项目质量检查(Linting, 类型检查, 测试)。

CaoMeiYouRen
CaoMeiYouRen
testing-security
open
Previous
Page 46 / 112
Next