code-quality
2
spec-verifier
Verify specification quality and completeness. Use after writing spec.md to ensure it meets standards before task breakdown - checks for clarity, feasibility, testability, and completeness.
korallis
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
2
pre-render-validate
Runs pre-render-validation.py and systematically fixes all detected errors. Use before rendering or committing to catch LaTeX, link, variable, citation, and import issues.
mikepsinn
testing-security
code-quality
2
refactorer
コード品質の問題を積極的に検出し改善する。以下を検出した際に自動発動: (1) 長いメソッド/クラス、(2) 重複コードパターン、(3) 深いネスト、(4) 不適切な命名、(5) マジックナンバー/文字列、(6) N+1 クエリパターン、(7) 未使用コード、(8) Feature Envy や God クラス。言語非依存のリファクタリングガイダンスを提供。
muryoimpl
testing-security
code-quality
2
code-quality-enforcement
Use when writing or modifying code. Enforces production-quality standards, prohibits common shortcuts, and ensures pre-existing issues are addressed. Invoked automatically by implementing-features and test-driven-development.
axiomantic
testing-security
code-quality
2
justfile-style
Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.
motlin
testing-security
code-quality
2
type-safety-mastery
Master type safety patterns - fix type errors at source, never use type: ignore or any, prefer Pydantic models, use type stubs for external libraries
andyngdz
testing-security
code-quality
2
typescript-coding-standards
TypeScript best practices, type system usage, and code quality standards
masanao-ohba
testing-security
code-quality
1
classifying-review-findings
Classifies code review findings into severity categories (CRITICAL, IMPORTANT, DEBT, SUGGESTED, QUESTION) following Bitwarden standards. Use when determining severity levels, categorizing PR comments, deciding what emoji to use, or verifying if something should be flagged at all.
bitwarden
testing-security
code-quality
1
dbt-development
Proactive skill for validating dbt models against coding conventions. Auto-activates when creating, reviewing, or refactoring dbt models in staging, integration, or warehouse layers. Validates naming, SQL structure, field conventions, testing coverage, and documentation. Supports project-specific convention overrides and sqlfluff integration.
rittmananalytics
testing-security
code-quality
1
database-fundamentals
Auto-invoke when reviewing schema design, database queries, ORM usage, or migrations. Enforces normalization, indexing awareness, query optimization, and migration safety.
DanielPodolsky
testing-security
code-quality
1
backend-fundamentals
Auto-invoke when reviewing API routes, server logic, Express/Node.js code, or backend architecture. Enforces REST conventions, middleware patterns, and separation of concerns.
DanielPodolsky
testing-security
code-quality
1
git-commit
Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.
bitbuilder-io
testing-security
code-quality
1
reviewing-content-governance
Reviews content against HMS IT governance standards including style guide, word list, and platform-specific guidelines. Checks voice and tone, word usage, formatting, structure, and compliance with content type requirements. Use when reviewing emails, knowledge base articles, website pages, or documents for style consistency, or when users mention "content review", "style guide check", "governance compliance", "editorial standards", "content quality", or "editorial review".
kynoptic
testing-security
code-quality
1
arcanea-code-review
Conduct thorough, constructive code reviews that improve code quality and team knowledge. Focuses on what matters - architecture, logic, security, maintainability - while avoiding bikeshedding.
frankxai
testing-security
code-quality
1
coding-style
Coding style for every case when coding. Use when coding.
stopsopa
testing-security
code-quality
1
umbraco-skill-code-analyzer
Analyze code examples in SKILL.md files for correctness using static analysis and TypeScript compilation
umbraco
testing-security
code-quality
1
setup-errors
Configure error handling infrastructure with custom error types and global handler. Use when adding error handling to a project. Triggers on "setup errors", "add errors", "error handling", "error infrastructure".
madooei
testing-security
code-quality
1
code-review
Perform comprehensive code review with best practices analysis
s1366560
testing-security
code-quality
1
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.
DanielPodolsky
testing-security
code-quality
1
tech-stack-constraints
Validate code and configurations against the allowed technology stack per constitution. Use when writing platform code, selecting libraries, or checking framework compliance.
zeeshan080
testing-security
code-quality
1
code-clean
Code quality review skill focusing on readability, maintainability, and consistency (non-architectural). Checks for naming conventions, code duplication, type consistency, unused code, and other clean code issues.
Chang-Yo
testing-security
code-quality
1
julik-frontend-races-reviewer
Use this agent when you need to review JavaScript or Stimulus frontend code changes with a special eye for race conditions. The agent should be invoked after implementing JavaScript features, modifying existing JavaScript code, or when creating or modifying Stimulus controllers. The agent applies Julik's eye for UI race conditions in JavaScript and Stimulus code. Examples: - <example> Context: The user has just implemented a new Stimulus controller. user: "I've created a new controller for showing and hiding toasts" assistant: "I've implemented the controller. Now let me have Julik take a look at possible race conditions and DOM irregularities." <commentary> Since new Stimulus controller code was written, use the julik-frontend-races-reviewer agent to apply Julik's uncanny knowledge of UI data races and quality checks in JavaScript and Stimulus code. </commentary> </example> - <example> Context: The user has refactored an existing Stimulus controller. user: "Please refactor the controller t
i3ringit
testing-security