Discover databases code quality skills, compare source repositories and read the instructions for each workflow.
Integrates Lighthouse CI for automated performance testing, Core Web Vitals tracking, and regression detection in CI/CD pipelines. Use when user asks to "setup Lighthouse CI", "add performance testing", "monito...
Review GitHub PRs with surgical precision. Flag only high-severity issues (bugs, security, performance, breaking changes) via succinct inline comments on specific lines. Skip style, nits, and minor improvements...
Transform AI markdown generation to be 100% markdownlint-compliant. Use this skill whenever generating messages containing markdown, generating or editing markdown files (.md) for technical documentation, READM...
Formats and validates JSON data. Use when you need to pretty-print JSON, fix formatting issues, or validate JSON syntax. ALWAYS USE THIS when doing JSON Formatting
Use when reviewing code changes, pull requests, or performing refactoring analysis with focus on patterns, security, and performance.
Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed. Triggers on keywords like "compare branches"...
Audit code for runtime safety and security vulnerabilities. Use when reviewing code, before commits, or performing security assessments.
Code quality and safety standards. Activates when editing or reviewing code. Use for quality priorities, safety checks, and code correctness verification.
Go development practices and tooling. Use when working with Go code (*.go files, go.mod, go.sum). Activates for Go code style, testing, linting, concurrency patterns, and Go idioms.
Use when performing coding tasks (implement features, fix bugs, refactor code). Orchestrates language detection, mode switching (normal/autopilot/full-auto), quality enforcement, and verification.
Review Go code for style, idioms, safety, and correctness. Use when reviewing Go code changes, pull requests, or auditing Go codebase quality.
General code review for staged changes or specified files. Use when reviewing pull requests, commits, or code changes across any language.
Lint and format Go code via golangci-lint. Use when asked to lint code, fix lint errors, or check code quality.
Develop, maintain, and audit Go analyzers (go/analysis). Use when creating/updating analyzers, suggested fixes, analysistest golden files, or integration analyzer harnesses.
Run full pre-commit workflow for Go code. Use when preparing to commit Go changes, before creating pull requests, or ensuring code quality.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage.
Go design patterns and refactoring skill. Use when refactoring complex code, reducing technical debt, or applying design patterns. Detects code smells and suggests pattern-based solutions.
GitHub PR utilities for code review workflows
Run Semgrep static analysis for fast security scanning and pattern matching. Use when asked to scan code with Semgrep, write custom YAML rules, find vulnerabilities quickly, use taint mode, or set up Semgrep in...
Run Gitleaks for hardcoded secrets detection in code and git history. Use when scanning for API keys, passwords, tokens, certificates, or sensitive credentials in source code and commit history.
systematic code review for correctness, security, style, and performance. Use this when the user asks for a review or before committing significant changes.
Apply UI and accessibility patterns. Uses accessibility, user-experience; invokes @designer, @reviewer for UI and a11y.
Apply language and framework coding standards. Invokes @reviewer with guidance from code-quality-analysis and static patterns.
Idiomatic Go patterns review. Use when checking Go-specific idioms, interface design, or pointer usage. Ensures code follows Go conventions and best practices.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.