mcpField
C
code-quality-workflow

code-quality-workflow

github.com/nickcrewTesting & quality6264 installsUpdated 17w ago
Repository

About code-quality-workflow

This skill provides a structured workflow for code analysis, review, and improvement, aimed at developers assessing quality or preparing changes for merge. It selects task-specific guidance and includes validation after improvements.

Key features

  1. 01Choose an analysis, review, or improvement mode
  2. 02Load task-specific reference guides
  3. 03Summarize and prioritize findings
  4. 04Validate improvements with tests or lint
  5. 05Report results and follow-up items

Use cases

  1. 01Assess code quality and document findings
  2. 02Review PRs or refactoring changes
  3. 03Check code before merging
  4. 04Improve maintainability or performance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nickcrew/claude-cortex --skill code-quality-workflow

After installing, type/code-quality-workflowin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
analyze-code.md
code-review.md
quality-improve.md

Details

From the project README

Code Quality Workflow

Overview

Standardize how to analyze, review, and improve code quality. This skill centralizes quality assessment, code review practices, and systematic improvements with validation gates.

When to Use

  • Quality assessment or code analysis requests
  • Code review (PRs, refactors, pre-merge checks)
  • Maintainability or performance improvements
  • Security hygiene improvements (non-audit level)

Avoid when:

  • A full security audit is required (use security-specific skills)
  • The task is purely dependency or artifact cleanup (use repo-cleanup)

Quick Reference

TaskLoad reference
Code analysisskills/code-quality-workflow/references/analyze-code.md
Code reviewskills/code-quality-workflow/references/code-review.md
Systematic improvementsskills/code-quality-workflow/references/quality-improve.md

Workflow

  1. Select the mode: analyze, review, or improve.
  2. Load the matching reference file for the expected structure.
  3. Inspect code and identify findings or opportunities.
  4. Apply changes (if improving) with safety validation.
  5. Verify with tests or lint as appropriate.
  6. Report findings, fixes, and follow-ups.

Output

  • Findings or improvements summary
  • Validation evidence or recommended checks
  • Follow-up backlog items if needed

Common Mistakes

  • Skipping severity prioritization
  • Mixing review and improvement without sign-off
  • Applying fixes without baseline tests
  • Overlapping with full security audit scopes

Comments

Markdown supported