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
12

javascript-coding-standards

JavaScript/ES6+ coding standards following Airbnb guidelines, modern patterns, React best practices, and comprehensive Jest testing. Use for JavaScript projects requiring clean, maintainable, production-ready code with modern tooling.

williamzujkowski
williamzujkowski
testing-security
open
code-quality
12

shellck

Run shellcheck on shell scripts after editing scripts or when debugging shell errors. Use for linting scripts in a repo (especially scripts/), catching issues like set -u with unset vars, bad subshell usage, or quoting mistakes.

regenrek
regenrek
testing-security
open
code-quality
12

review-codex

Final code/plan review using Codex. Use as the last review step after sonnet and opus.

Z-M-Huang
Z-M-Huang
testing-security
open
code-quality
11

commitlint

When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.

Jamie-BitFlight
Jamie-BitFlight
testing-security
open
code-quality
11

pr-reviewer

Review a pull request for correctness, regressions, and missing tests. Use when a mid-level developer needs structured review guidance.

proflead
proflead
testing-security
open
code-quality
11

quality-complexity-check

Analyze code complexity metrics including cyclomatic complexity and nesting depth. Use to identify code that needs refactoring.

mvillmow
mvillmow
testing-security
open
code-quality
11

review

epistemic standards for evaluation and analysis. load before reviewing code, debugging, reporting findings, or any task where claims must be defensible. enforces trace-or-delete, confidence labeling, falsification.

bdsqqq
bdsqqq
testing-security
open
code-quality
11

doc-validate-markdown

Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.

mvillmow
mvillmow
testing-security
open
code-quality
11

quality-security-scan

Scan code for security vulnerabilities and unsafe patterns. Use before committing sensitive code or in security reviews.

mvillmow
mvillmow
testing-security
open
code-quality
11

mojo-type-safety

Validate type safety in Mojo code including parametric types and trait constraints. Use during code review or when type errors occur.

mvillmow
mvillmow
testing-security
open
code-quality
11

mojo-lint-syntax

Validate Mojo syntax against current v0.26.1+ standards. Use to catch syntax errors before compilation.

mvillmow
mvillmow
testing-security
open
code-quality
11

security-scan

Run comprehensive security vulnerability scans when reviewing code. Automatically uses basic mode (fast, high/medium severity only) for first reviews, advanced mode (comprehensive, all severities) for iterations. Detects SQL injection, XSS, hardcoded secrets, insecure dependencies. Use before approving any code changes or pull requests.

mehdic
mehdic
testing-security
open
code-quality
11

mojo-format

Format Mojo code using mojo format command. Use when preparing code for commit or when formatting checks fail.

mvillmow
mvillmow
testing-security
open
code-quality
11

validate-inputs

Check function inputs for correctness and safety. Use when implementing defensive programming.

mvillmow
mvillmow
testing-security
open
code-quality
11

run-precommit

Run pre-commit hooks locally or in CI to validate code quality before committing. Use to ensure commits meet quality standards and CI will pass.

mvillmow
mvillmow
testing-security
open
code-quality
11

debug-eval

Diagnose and fix Nix evaluation errors, build failures, and module conflicts.

codgician
codgician
testing-security
open
code-quality
11

validate-mojo-patterns

Validate Mojo code patterns (out self, mut, List, etc.) against best practices. Use to ensure code follows project standards.

mvillmow
mvillmow
testing-security
open
code-quality
11

security-quick-scan

Scan code or configuration for common security issues. Use when a mid-level developer needs a quick security pass.

proflead
proflead
testing-security
open
code-quality
11

quality-run-linters

Run all configured linters including mojo format, markdownlint, and pre-commit hooks. Use before committing code to ensure quality standards are met.

mvillmow
mvillmow
testing-security
open
code-quality
11

accessibility-basic-check

Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.

proflead
proflead
testing-security
open
code-quality
11

conducting-code-review

Complete workflow for conducting thorough code reviews with structured feedback

cipherstash
cipherstash
testing-security
open
code-quality
11

agent-validate-config

Validate agent YAML frontmatter and configuration. Use before committing agent changes or in CI.

mvillmow
mvillmow
testing-security
open
code-quality
11

lint-code

Check code for style and quality issues. Use when validating code before commits.

mvillmow
mvillmow
testing-security
open
code-quality
10

documentation-structure-validator

Validate documentation structure, check for missing sections, verify markdown syntax, ensure consistency with templates. Use when user mentions docs validation, structure check, README review, documentation quality, or wants to verify documentation completeness.

mverab
mverab
testing-security
open
Previous
Page 58 / 112
Next