Results for “quality-audit”

Audits a repository for comment coverage and brings under-commented source files up to standard, one file at a time, with a resumable tracker.

Coordinates five specialized coding agents (linter, perf, refactor, security, test) to enforce quality gates across the development lifecycle, from lint enforcement through performance profiling, refactoring, security auditing, and test coverage.

Conducts multi-axis code review across correctness, readability, architecture, security, and performance before merging any change.

Audits test files for anti-patterns and quality issues, producing a severity-ranked report across multiple languages and frameworks.

Use when auditing Claude skills and commands for quality. Supports Quick Scan (changed skills only) and Full Stocktake modes with sequential subagent batch evaluation.

Use when auditing Claude skills and commands for quality. Supports Quick Scan (changed skills only) and Full Stocktake modes with sequential subagent batch evaluation.

Quality Gates

Review local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist-driven process.

QA Testing

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist and attack surface mapping.

"Quality" is unmanageable until it is a set of numbers with agreed definitions.

5 维度质量评审和 Anti-Slop 检测框架，用于确保设计产出达到品牌级水准。 包含评审标准、检测清单、评分规则和修复建议模板。 触发词：质量审查、评审、Anti-Slop、检测、评分、门控

Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues.

Systematically QA test a web application and fix bugs found. (gstack)

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, using a structured checklist and verification process.

Applies four disciplined mindsets—audit, debt, help, review—to cut complexity, track deferrals, surface reference, and catch over-engineering in codebases.

Performs structured code reviews of git branches, tracking findings in a living document and optionally running deep architectural analysis with subagents.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, producing a prioritized report with severity ratings and concrete fixes.

Automates end-to-end QA: starts the app, exercises screens and API endpoints, verifies functionality and design quality, runs domain analysis, and fixes issues found.

Reviews staged and unstaged code changes for security vulnerabilities, code quality issues, and adherence to project conventions, reporting findings by severity.

>- Advanced Product Quality Planning (APQP) — plan and track a new product launch through all 5 phases, identify deliverables per phase, run gate reviews, and ensure quality outputs are complete before Start of Production (SOP). Use when launching a new part, managing an APQP project, or auditing APQP completeness. Covers AIAG APQP 2nd edition and IATF 16949 §8.3.

Audits test code in any language using the academic testsmells.org 19-smell catalog, producing a severity-ranked report with specific locations and actionable fixes.

Scans Python and JavaScript codebases for bugs, security vulnerabilities, code smells, and anti-patterns, producing a prioritized fix list with line numbers, severity ratings, and suggested corrections.

Review technical and strategy documents for codebase drift, strategic alignment, cross-document conflicts, simplification opportunities, engineering quality, and document organization. Use when auditing whether docs should be kept, updated, merged, split, moved, archived, or deleted.