SuperAPI AI Directory

Quality Tools

Coding & development

View repository

Updated 10-16 05:58

About this skill

<refactoring_operations> A catalog of language-neutral operations that raise cohesion and testability. Each is a bounded, behavior-preserving move; apply the smallest one that addresses the finding rather than a broad rewrite.

<scored_review> Output skeleton for a multi-dimensional quality review (performance, documentation, or general design). It turns a diffuse "review" into a prioritized, actionable report. Score each dimension separately on a fixed scale (for example N dimensions each out of 100) with a one-line status per dimension, so weak areas stay visible rather than being averaged away. Separate findings into Critical (must fix before release) and Quick Wins (high impact, low effort), each with an effort estimate. Sequence remediation into phases (for example reliability first, then performance, then testing, then advanced), so the report reads as a rollout plan rather than a flat list. State the analysis's basis and its limits: an architectural or static review is not runtime measurement. Do not present estimated improvements or scores as measured results. Give an explicit confidence level and its known limitations (what was not exercised: real workloads, low-resource systems, actual profiling). </scored_review>

<decision_tree name="tool_selection"> What type of quality check is needed? Use language-specific type checker (tsc, mypy, cargo check) Use linter (eslint, clippy, ruff, biome lint) Use formatter (prettier, ruff format, cargo fmt, biome format) Use biome check (single tool for both) Run in sequence: types → lint → format </decision_tree>

<best_practices> Run type checker before linter for faster feedback Verify with tests after auto-fixes Use project-specific configuration when available Report all issues with file:line locations Run incremental checks for large codebases Separate formatting from logic changes in commits Prefer the smallest cohesion-raising refactor operation (view-data extraction, barrel removal, helper split) over a broad rewrite, and verify behavior with targeted tests after each move (refactoring_operations) For scored reviews, separate Critical from Quick Wins, phase the rollout, and state the analysis basis and its limits honestly (scored_review) </best_practices>

<anti_patterns> Auto-fixing without reviewing changes Review auto-fix changes, run tests after

<error_escalation inherits="core-patterns#error_escalation"> Minor linting warning with no functional impact Type error or test failure blocking CI Code quality gate failure preventing deployment Security vulnerability detected by static analysis </error_escalation>

<related_skills> Run tests after quality fixes Integration with implementation workflow </related_skills> <related_agents> Locate code patterns and references in this skill domain Review implementation quality against this skill guidance Analyze code complexity and suggest refactoring improvements </related_agents>