code-quality
4
restructured-text
Guidelines for writing valid reStructuredText (.rst) in this repo (Sphinx).
Liam-Deacon
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
4
wordpress-docs-review
Review and validate WordPress documentation against official style guide standards. Use when reviewing documentation for WordPress core, themes, plugins, or related projects. Checks compliance with voice/tone, accessibility, inclusivity, code formatting, and technical writing standards.
fellyph
testing-security
code-quality
4
issue-reviewer
Automatically reviews code changes against issue/spec at evaluate phase start to ensure implementation completeness
fractary
testing-security
code-quality
4
doc-validator
Validates documentation against type-specific rules and schemas loaded dynamically, checking frontmatter, structure, content, and schema compliance
fractary
testing-security
code-quality
4
game-systems-code-review
Review code changes for game/engine systems with a focused Game Systems Engineer mindset. Use when the user asks to review code, check consistency, or validate changes against AGENTS.md standards, especially for C++ engine, threading, performance, or systems behavior.
Ronin15
testing-security
code-quality
4
hammer-build-validate
Runs complete build validation pipeline for SDL3 HammerEngine including Debug build, smoke test execution, core test suite, and summary report generation. Use when the user wants to quickly validate their changes, check if the codebase is in a good state, or run the standard daily validation workflow.
Ronin15
testing-security
code-quality
4
dependency-auditing
依存関係の脆弱性検出、評価、修正計画を体系化するスキル。 CVSS評価と修正優先度を整理し、継続的な監査を支援する。 Anchors: • CVSS v3.1 Specification / 適用: 重大度評価 / 目的: 優先度の整合性 • The Pragmatic Programmer / 適用: 自動化と継続改善 / 目的: 監査の継続性 • OWASP Dependency-Check / 適用: 依存監査 / 目的: 脆弱性検出の標準化 Trigger: Use when auditing dependencies, evaluating vulnerability reports, prioritizing remediation, or integrating security scans into CI/CD. dependency audit, CVE, GHSA, CVSS, npm audit, pnpm audit, security scanning
daishiman
testing-security
code-quality
4
markdown-formatter
Formats markdown files according to best practices and common style guidelines. Use when cleaning up markdown documentation, ensuring consistent formatting, or standardizing README files.
markpitt
testing-security
code-quality
4
typescript-import-style
Apply import formatting and ordering rules that minimize merge conflicts when multiple developers or parallel agents modify the same file. Enforces one-import-per-line, alphabetical sorting, and consistent grouping.
jpoutrin
testing-security
code-quality
4
arch-check
Verify architecture health including layer violations, circular dependencies, package structure, and design pattern compliance
pwittchen
testing-security
code-quality
4
go-analyzer-dev
Develop, maintain, and audit Go analyzers (go/analysis). Use when creating/updating analyzers, suggested fixes, analysistest golden files, or integration analyzer harnesses.
mway
testing-security
code-quality
4
code-quality
Code quality - patterns, testing, maintainability. Use for code review.
SylphxAI
testing-security
code-quality
4
python-code-review
Python-specific code review guidelines covering common bugs, security issues, performance anti-patterns, and framework-specific concerns for Django, FastAPI, and Celery. Use when reviewing Python code changes for quality, security, and best practices.
jpoutrin
testing-security
code-quality
4
json-formatter
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
thomasholknielsen
testing-security
code-quality
3
output-style-audit
Validates output-style persona definitions, behavior specifications, and keep-coding-instructions decisions. Use when auditing, reviewing, or improving output-styles, checking persona clarity, validating behavior concreteness, or verifying scope alignment (user vs project). Triggers when user asks about output-style best practices or needs help with persona definition.
philoserf
testing-security
code-quality
3
command-audit
Audits command files for correctness and best practices. Use when reviewing, improving, or validating commands, checking frontmatter, assessing structure, or learning command quality standards.
philoserf
testing-security
code-quality
3
python-engineering
Python development utilities including linting, testing, and Pydantic standards
tao3k
testing-security
code-quality
3
code-review
Best practices for performing thorough, constructive code reviews. Use when reviewing PRs to ensure quality feedback that improves code and helps developers grow.
shwilliamson
testing-security
code-quality
3
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.
BbgnsurfTech
testing-security
code-quality
3
000-jeremy-content-consistency-validator
Validate messaging consistency across website, GitHub repos, and local documentation generating read-only discrepancy reports. Use when checking content alignment or finding mixed messaging. Trigger with phrases like "check consistency", "validate documentation", or "audit messaging".
BbgnsurfTech
testing-security
code-quality
3
documenting-code-comments
Standards for writing self-documenting code and best practices for when to write (and avoid) code comments. Use when auditing, cleaning up, or improving inline code documentation.
third774
testing-security