'quality' 검색 결과

Systematic code cleanup and refactoring agent that identifies and fixes code quality issues without changing functionality. Focuses on: - Dead code removal - Import organization - Type improvements - Consistent patterns - File organization Use when "User asks to "clean up" code, User mentions "dead code" or "unused", User wants to "organize imports", User asks about "code quality", User wants to "refactor" without changing behavior, Code review identifies cleanup items, After major feature completion, cleanup, refactoring, code-quality, maintenance, organization" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code review specialist for quality standards, design patterns, security review, and constructive feedbackUse when "code review, pull request, PR review, code quality, refactor, technical debt, design pattern, best practice, code-review, quality, patterns, security, refactoring, best-practices, pull-request, review, ml-memory" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and response schema completeness. Produces a polished interactive HTML report with a summary scorecard, site-wide pattern analysis, ranked top issues, and per-endpoint findings with specific fix guidance. Trigger this skill whenever a user provides a documentation URL and asks to audit, review, analyse, or check their API docs. Also trigger for: "do the same audit for X", "audit docs.company.com", "check the API docs at X", "run the API docs audit on X", "review the docs for Y API", or pastes a URL alongside words like audit, review, crawl, check, analyse, quality, completeness, or gaps. Always use this skill — do not attempt the audit without following this structured crawl-score-report workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit existing API quality controls — find missing lint rules, gaps in CI gates, and quality debt. Use when asked to "audit our API quality controls", "find missing lint rules", or "assess our API governance".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit existing data cleaning code — find missing validation, silent data loss, and quality gaps. Use when asked to "audit our data cleaning", "are we losing data silently", or "find data quality gaps".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design a data validation pipeline — schema checks, range validation, and quality metrics. Use when asked to "validate incoming data", "add schema checks", or "define data quality metrics".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluate a single skill's quality against its stated purpose. Classifies the skill's purpose type, then scores applicable quality categories — universal dimensions always apply; structural dimensions (scripts, references, assets) are scored only when warranted by the skill's purpose. A focused 20-line behavioral skill with no bundled resources scores fully on all applicable categories. Use when auditing skill quality, checking marketplace readiness, evaluating skill completeness, performing pre-publication evaluation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drive a PR to a green quality gate and keep it there. Loops on SonarCloud for the project's targets, no new issues, no duplication on new code, and coverage on new logic as close to 100% as the code allows, then watches the PR checks until every one passes. Use when a quality gate blocks a merge, when coverage or duplication has to come up, or before asking for review. Triggers - "fix the sonar issues", "quality gate", "get coverage up", "zero duplication", "loop until CI is green", "watch the checks".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

VNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX governance state. Triggers include: editing intelligence injection code, querying central DB for cross-project insights, debugging "intelligence not appearing in T0 state", modifying schema in `schemas/quality_intelligence.sql` or `schemas/runtime_coordination_v*.sql`, working with `scripts/quality_db_init.py` or `scripts/lib/coordination_db.py`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

VNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on quality_intelligence.db / runtime_coordination.db / dispatch_tracker.db, code_snippets FTS5, snippet_metadata linkage, success_patterns / antipatterns, T0 state projection (t0_state.json), intelligence_injections lifecycle, dispatch → receipt → events → archive flow, central state architecture, project_id propagation across VNX, or any code that reads/writes VNX governance state. Triggers include: editing intelligence injection code, querying central DB for cross-project insights, debugging "intelligence not appearing in T0 state", modifying schema in `schemas/quality_intelligence.sql` or `schemas/runtime_coordination_v*.sql`, working with `scripts/quality_db_init.py` or `scripts/lib/coordination_db.py`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js), Brandur Leach (Postgres), Vercel Performance, Simon Willison (LLM pipelines), Karri Saarinen (UI quality), Vitaly Friedman (UX quality), Kent Beck (test quality). Uses parallel subagents for deep, independent review. Produces prioritised P1/P2/P3 findings. Stack: Next.js App Router / React / TypeScript / tRPC / Prisma / Neon / Clerk.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code quality assurance strategies. Parent skill for quality-related skills: security (security review) and debug (systematic debugging).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. Use when a .NET repo needs an explicit quality stack in `AGENTS.md`, docs, or pipeline YAML.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides code quality principles including SOLID, DRY, testing strategies, and best practices for implementation review. Use when reviewing code or applying quality standards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a data analysis for quality, correctness, and reproducibility. Covers data quality assessment, assumption checking, model validation, data leakage detection, and reproducibility verification. Use when reviewing a colleague's analysis before publication, validating an ML pipeline before production deployment, auditing a report for regulatory or business decision-making, or performing a second-analyst review in a regulated environment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate and edit high-quality images using Google's Nano Banana Pro (Gemini 3 Pro Image) AI model. Use this skill when working with AI image generation or editing tasks including (1) Creating images from text prompts with professional quality, (2) Editing existing images with natural language instructions, (3) Multi-turn iterative image refinement, (4) Product photography and marketing visuals, (5) Creating infographics and diagrams with text, (6) Photorealistic and artistic image generation, (7) Batch image generation workflows, (8) Testing and troubleshooting Gemini image generation API. Supports up to 4K resolution, multiple aspect ratios, reference images, and advanced prompting techniques for cinema-quality results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when scoring finished content against quality dimensions, evaluating whether a piece meets publishable standards, or determining which workflow phase needs rework based on quality gaps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. Use when a .NET repo needs an explicit quality stack in `AGENTS.md`, docs, or pipeline YAML.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply the SERVQUAL model (Parasuraman, Zeithaml, and Berry, 1988) to measure service quality gaps across five dimensions. Use this skill when the user needs to diagnose service quality shortfalls, benchmark customer expectations against perceptions, design service improvement programs, or when they ask 'where is our service failing', 'what do customers expect vs experience', or 'how do we measure service quality'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply the DeLone and McLean Information Systems Success Model to evaluate IS effectiveness through six interdependent dimensions. Use this skill when the user needs to assess system quality, information quality, or service quality of an IS, diagnose why users are dissatisfied, measure net benefits of a system investment, or when they ask 'how do we measure IS success', 'why are users unhappy with this system', or 'is our system delivering value'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate TypeScript/JavaScript code quality with ESLint, Prettier, type checking, and security analysis. Use for TypeScript/JS codebases to ensure code quality and standards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate Python code quality with formatting, type checking, linting, and security analysis. Use for Python codebases to ensure PEP 8 compliance, type safety, and code quality.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.