Apply this repository's coding conventions and patterns. Use when writing or reviewing code in this codebase to ensure consistency with established patterns for DI, logging, error handling, testing, and documentation. Auto-trigger when implementing features, fixing bugs, or reviewing code changes.

Nikola-Milovic

testing-security

open

code-quality

ast-grep-code-analysis

Use when analyzing complex codebases for security vulnerabilities, performance issues, and structural patterns - provides systematic AST-based approach using ast-grep for comprehensive code understanding beyond manual inspection

zenobi-us

testing-security

open

code-quality

checking-files-with-lsp

Use when you need to check, verify, validate or understand code or structure of a file (often code related files or markdown) - automatically detects file type, finds appropriate LSP/linter in mise, and runs validation

zenobi-us

testing-security

open

code-quality

increment-quality-judge-v2

Enhanced AI-powered quality assessment with RISK SCORING (BMAD pattern) and quality gate decisions. Evaluates specifications, plans, and tests for clarity, testability, completeness, feasibility, maintainability, edge cases, and RISKS. Provides PASS/CONCERNS/FAIL decisions. Activates for validate quality, quality check, assess spec, evaluate increment, spec review, quality score, risk assessment, qa check, quality gate, /sw:qa command.

anton-abyzov

testing-security

open

code-quality

workflow-validation

Validates workflow schemas, expressions, and block configurations in seer. Use when reviewing workflow changes, adding new blocks, debugging workflow compilation errors, or validating workflow JSON structures.

seer-engg

testing-security

open

code-quality

code-review

Lightweight code review for diffs/PRs focusing on high-signal simplifications, code smells, security, performance, and whether new tests are needed; focus on recently modified code unless instructed otherwise.

mzbac

testing-security

open

code-quality

ci-pr-helper

Run local test/style checks and open GitHub PRs for lance-context. Use when asked to run CI-equivalent checks (uv pytest, ruff/pyright, cargo fmt/clippy/test) and then create a PR with a proper title/body.

lance-format

testing-security

open

code-quality

code-check

Validate and lint code after changes. Use after editing Rust/TypeScript files, when user mentions compilation errors, type checking, linting, clippy warnings, or before commits/PRs. Ensures all code passes checks and has zero warnings.

edgeandnode

testing-security

open

code-quality

feature-fmt-check

Validate feature doc format against .patterns/feature-docs.md. Use when reviewing PRs, after editing feature docs, or before commits

edgeandnode

testing-security

open

code-quality

code-review

Proactive code quality review. Triggers on significant code changes to check security, performance, architecture, and project patterns.

muyen

testing-security

open

code-quality

tidying

Guide structural code improvements using Kent Beck's Tidy First methodology. Use when seeing messy code, before making behavioral changes, after completing features, or discussing when to clean up code.

atusy

testing-security

open

code-quality

woocommerce-dev-cycle

Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow in WooCommerce projects.

secondsky

testing-security

open

code-quality

verification-before-completion

Run verification commands and confirm output before claiming success. Use when about to claim work is complete, fixed, or passing, before committing or creating PRs.

secondsky

testing-security

open

code-quality

obsidian-markdown-structure

Validate and enforce markdown document structure including frontmatter positioning, heading hierarchy, and content organization. Use when creating or validating markdown files.

jykim

testing-security

open

Page 55 / 112