code-quality
90
lint-dotnet
Run .NET architecture linter to check for MSBuild/CPM violations
aiskillstore
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
90
error-handling-fundamentals
Auto-invoke when reviewing try/catch blocks, API error responses, async operations, or user feedback patterns. Enforces graceful degradation and meaningful error messages.
aiskillstore
testing-security
code-quality
90
neovim-debugging
Debug Neovim/LazyVim configuration issues. Use when: user reports Neovim errors, keymaps not working, plugins failing, or config problems. Provides systematic diagnosis through hypothesis testing, not just checklists. Think like a detective narrowing down possibilities.
aiskillstore
testing-security
code-quality
90
validate-requirements
Validate that input meets prerequisites based on the user's saved standards for the project type. Use at the start of any quality pipeline to ensure the user has provided sufficient requirements.
aiskillstore
testing-security
code-quality
90
chapter-analyzer
Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.
aiskillstore
testing-security
code-quality
90
typescript-strict
Enforce TypeScript strict mode and type safety. Use when setting up projects, reviewing code, or when type errors are ignored. Covers strict flags, no-any rules, and type inference best practices.
aiskillstore
testing-security
code-quality
90
requesting-code-review
Request and process code reviews with proper context. Use after completing significant implementation work.
aiskillstore
testing-security
code-quality
90
quality-gates
Run comprehensive quality checks including linting, type checking, tests, and security audits before commits or deployments
aiskillstore
testing-security
code-quality
90
code-reviewer
Provides thorough code review guidance when users ask for code reviews, PR reviews, or feedback on their code. Activates when users mention reviewing code, checking for issues, or want feedback on implementations.
aiskillstore
testing-security
code-quality
90
container-hadolint
Dockerfile security linting and best practice validation using Hadolint with 100+ built-in rules aligned to CIS Docker Benchmark. Use when: (1) Analyzing Dockerfiles for security misconfigurations and anti-patterns, (2) Enforcing container image security best practices in CI/CD pipelines, (3) Detecting hardcoded secrets and credentials in container builds, (4) Validating compliance with CIS Docker Benchmark requirements, (5) Integrating shift-left container security into developer workflows, (6) Providing remediation guidance for insecure Dockerfile instructions.
aiskillstore
testing-security
code-quality
90
verification-before-completion
Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.
aiskillstore
testing-security
code-quality
90
no-hardcoding
Forbid hardcoded values in code. Use this when reviewing code, writing new features, or when magic numbers/strings are detected. Enforces constants, env variables, and config files.
aiskillstore
testing-security
code-quality
90
completion-integrity
Prevents shortcuts and cheating when completing tasks. Blocks commits with warning suppressions, commented tests, or deleted assertions.
aiskillstore
testing-security
code-quality
90
typescript-best-practices
Provides TypeScript patterns for type-first development, making illegal states unrepresentable, exhaustive handling, and runtime validation. Must use when reading or writing TypeScript/JavaScript files.
aiskillstore
testing-security
code-quality
90
code-analysis
Check if code is readable by non-developers - clear names, plain English comments, no jargon
aiskillstore
testing-security
code-quality
90
error-handling-gate
Verify errors are handled gracefully with meaningful user feedback. Issues result in WARNINGS.
aiskillstore
testing-security
code-quality
90
skill-auditor
Audits and validates skill definitions for quality, completeness, and best practices. Use when reviewing existing skills for proper formatting, evaluating if skills should be split into sub-skills, or ensuring skills follow established conventions.
aiskillstore
testing-security
code-quality
90
code-consistency-validator
Validates type consistency across Rust, TypeScript, PostgreSQL boundaries. Use when reviewing code, debugging type mismatches, or validating API contracts. Triggers on: check consistency, validate types, find mismatches, cross-language.
aiskillstore
testing-security
code-quality
90
code-review-standards
Code review framework and criteria. References security-sentinel for security checks. Use when performing code reviews or defining review standards.
aiskillstore
testing-security
code-quality
90
quality-fixer
Automatically apply safe quality fixes including formatting (Black, isort), linting (Ruff auto-fixes), and resolve formatter conflicts. Use when quality checks fail or before committing code.
aiskillstore
testing-security
code-quality
90
creating-claude-hooks
Use when creating or publishing Claude Code hooks - covers executable format, event types, JSON I/O, exit codes, security requirements, and PRPM package structure
aiskillstore
testing-security
code-quality
90
ownership-gate
Verify the junior can explain and defend every line of code they wrote. This gate BLOCKS completion if failed.
aiskillstore
testing-security