code-quality

Solid

Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).

Code & Development 25 stars 4 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
47
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

<objective> Code Quality is the canonical 7-phase validation workflow shared with the `sniper` agent (this skill and `agents/sniper.md` must stay in sync): explore architecture, research documentation, analyze impact via Grep usages, detect duplication with jscpd (DRY), detect errors via linters, apply precision corrections informed by docs/impact/DRY findings, then re-verify until linters, tests, and duplication are all clean. It covers SOLID compliance, DRY thresholds, error priority (security/logic/performance/style), file-size limits, and architecture-pattern violations across all languages. It validates quality AFTER the fact -- it does not confirm the original problem was actually solved. Run the `verification` skill first to confirm functional resolution, then code-quality to confirm the fix is clean. </objective> # Code Quality Skill Canonical workflow definition: `agents/sniper.md` (this skill and the sniper agent share the same 7-phase workflow — update both together). ## 🚨 MANDATORY 7-PHASE WORKFLOW ``` PHASE 1: Exploration (explore-codebase) → BLOCKER PHASE 2: Documentation (research-expert) → BLOCKER PHASE 3: Impact Analysis (Grep usages) → BLOCKER PHASE 3.5: DRY Detection (jscpd duplication) → NON-BLOCKING PHASE 4: Error Detection (linters) PHASE 5: Precision Correction (with docs + impact + DRY) PHASE 6: Verification (re-run linters, tests, duplication) ``` **CRITICAL**: Phases 1-3 are BLOCKERS. Never skip them. **DRY**: Phase 3.5 is non-blocking but fin...

Details

Author
fusengine
Repository
fusengine/agents
Created
8 months ago
Last Updated
6 days ago
Language
CSS
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

code-quality

Language-agnostic skill for authoring and reviewing code with low cognitive complexity, readability, and long-term maintainability. Covers guard clauses, single-responsibility functions, type-driven design (illegal states unrepresentable, branded primitives, discriminated unions), schema-first validation, single source of truth for union metadata, functional core + imperative shell, idempotency, and neighbour-pattern symmetry. Pairs with `tdd` for new code (rules apply in GREEN/REFACTOR). Stack-specific extensions live under `rules/stacks/<stack>/` (React, Next.js today; drop a subdirectory for any other language or framework). Use during PR review, after writing new code, in TDD GREEN/REFACTOR, or when asked to "improve quality", "make this readable", "reduce complexity", "deduplicate", "clean this up", or "/code-quality".

13 Updated yesterday
mthines
Code & Development Listed

code-quality

Analyzes code quality, complexity, duplication, and architectural patterns. Use after implementing features, during code review, or when preparing for PR. Auto-invoke when user has completed significant code changes or asks to review code quality.

4 Updated 3 weeks ago
joris887
AI & Automation Listed

code-verifier

Use when running a full quality gate after implementation — lint, type-check, tests, and import validation. Mandatory step in job-orchestrator after task-implementer and after fix iterations. Use standalone when you need a structured verification report.

1 Updated 1 weeks ago
MrCipherSmith