check-doc-consistency
Check consistency of project documentation and propose fixes.
Script and automate repetitive tasks and workflows.
Check consistency of project documentation and propose fixes.
Security scanning patterns using gitleaks, PII detection, and secret scanning. Use when writing scripts that handle sensitive data, committing code, or setting up security automation. Includes gitleaks configuration, custom PII rules, and pre-commit hooks.
Proactively suggests tests when code changes are detected. Activates when functions are created, logic is modified, security-sensitive code is added, or bug fixes are implemented. Provides non-intrusive test recommendations to help vibe coders ship with confidence.
Review all .md files for naming conventions, conciseness, consistency, and completeness. Use when creating or editing any markdown file.
Use this skill to validate code changes pass all checks (format, lint, build, tests). Runs validation script and iteratively fixes failures. Invoke before finalizing PRs or after making code changes.
[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.
Performs comprehensive code reviews following industry best practices. Use when reviewing pull requests, code changes, or when asked to analyze code quality, security, performance, or maintainability. Checks for common bugs, security vulnerabilities, code smells, and adherence to coding standards.
Comprehensive Nix validation: treefmt-nix integration, statix/deadnix linting, flake checks, aytordev-specific patterns. Use when validating Nix code or setting up linting infrastructure.
Audits Go code for error handling best practices - proper wrapping with %w, preserved context, meaningful messages, no error swallowing. Use before committing Go code or during error handling reviews.
Opinionated constraints for writing maintainable, testable code. Apply MTE principles, avoid over-engineering, guide refactoring, and provide code review checklists. Use when users write code, refactor, or need code review. Triggers on keywords like "code quality", "refactor", "review", "MTE", "代码质量", "重构", "审查".
Mandatory verification protocol after code changes for JavaScript/TypeScript projects. Use after any code modification to ensure quality.
ALWAYS use this skill proactively for Consumer Affairs Django repositories (located in ../ca/ directory) when ANY of these occur - (1) After writing or modifying ANY Python code files in CA repos (2) After tests pass and before telling user work is complete (3) User mentions linting, formatting, ruff, code style, or code quality (4) After using the ca-django-tests skill successfully (5) Before preparing to commit code. This skill runs 'ca exec ruff format' and 'ca exec ruff check --fix' to ensure code quality. CRITICAL - Always run this automatically after code changes and before declaring work complete.
Spawns 4 parallel review agents (Accessibility, React Router, React Core, Anders Hejlsberg) to conduct comprehensive multi-perspective code reviews
Review Vendure plugins for best practices violations. Detects missing decorators, improper DI, hardcoded config, lifecycle hook issues, and service anti-patterns. Use when reviewing plugin PRs or auditing plugin quality.
TypeScript conventions for ecommerce monorepo. Covers Next.js, Fastify, Prisma, Zod validation, React Query, and testing patterns. Triggers on "typescript", "type error", "ts", "tsx", "type hints", "zod schema", "prisma", "react query", "next.js", "fastify routes", "api types". PROACTIVE: MUST invoke when writing or editing .ts or .tsx files.
Automatically applies when reviewing code. Ensures structured review checklist covering correctness, security, performance, maintainability, testing, and documentation.
Deep audit of the NET-NiNJA repository to map architecture, entrypoints, dead code, missing wiring, broken imports, duplicated logic, TODOs, placeholder handlers, and GUI elements without backend actions. Use when asked to review the repo structure or produce an audit report, punch list with file/line refs, dependency graph, or known entrypoints list.
Use when creating PRs to enforce code quality standards. Automated detection of anti-patterns, security issues, and code smells. Python 3.8+
Code review and audit agent for pull requests and code quality
Review implementation for code quality, style consistency, and best practices. Runs before security review. READ-ONLY - reports issues but does not fix them.
Write clean, consistent code following established naming conventions, formatting standards, and the DRY principle with meaningful names and small focused functions. Use this skill when writing or editing any code file in any programming language. When naming variables, functions, classes, or files. When formatting code, organizing imports, or structuring functions. When refactoring code to remove duplication or dead code. When ensuring consistent indentation, code style, and readability. This skill applies universally to all code files including `.js`, `.ts`, `.py`, `.rb`, `.java`, `.go`, `.php`, and any other programming language files.
Review code for dealflow-network project conventions, error handling, type safety, and best practices. Use when reviewing pull requests, checking code quality, or validating implementations. This skill is read-only and will not modify files.
Comprehensive Ruby and Rails code review using Sandi Metz rules and SOLID principles. Automatically runs rubycritic and simplecov, analyzes changed files in current branch vs base branch, identifies OOP violations, Rails anti-patterns, security issues, and test coverage gaps. Outputs REVIEW.md with VSCode-compatible file links. Use when reviewing Ruby/Rails code, conducting code reviews, checking for design issues, or when user mentions code review, pull request review, or code quality analysis.