How do I decide which mode to use?

Use analyze for assessments, review for PR-level checks, improve for changes with validation gates.

What if I find critical issues?

Prioritize by severity, validate with tests, and obtain sign-off before applying fixes.

Is this suitable for full security audits?

It covers non-audit level security hygiene; for full security audits use dedicated security skills.

code-quality-workflow

Scanned

npx machina-cli add skill NickCrew/claude-cortex/code-quality-workflow --openclaw

Files (1)

SKILL.md

1.7 KB

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

Task	Load reference
Code analysis	`skills/code-quality-workflow/references/analyze-code.md`
Code review	`skills/code-quality-workflow/references/code-review.md`
Systematic improvements	`skills/code-quality-workflow/references/quality-improve.md`

Workflow

Select the mode: analyze, review, or improve.
Load the matching reference file for the expected structure.
Inspect code and identify findings or opportunities.
Apply changes (if improving) with safety validation.
Verify with tests or lint as appropriate.
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

Source

git clone https://github.com/NickCrew/claude-cortex/blob/main/skills/code-quality-workflow/SKILL.mdView on GitHub

Overview

Code Quality Workflow standardizes how to analyze, review, and improve code quality. It centralizes quality assessment, code review practices, and systematic improvements with validation gates that ensure changes are safe and verifiable.

How This Skill Works

Choose the mode: analyze, review, or improve; load the matching reference file; inspect code and identify findings; apply changes with safety validation; verify with tests or lint; report findings and follow-ups.

When to Use It

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

Quick Start

Step 1: Select mode (analyze, review, improve) and load the proper reference file
Step 2: Inspect code, identify findings, and plan changes with validation gates
Step 3: Apply changes (if improving), run tests/lint, and report findings with follow-ups

Best Practices

Prioritize findings by severity and impact
Keep analysis, review, and improvements clearly separated with sign-off
Run baseline tests and lint before applying fixes
Use the appropriate reference files for expected structure
Document validation results and follow-up backlog

Example Use Cases

Analyzing a legacy module to identify maintainability hotspots and propose refactors with test coverage
Reviewing a PR for naming consistency, duplication, and lint issues, with checklist
Running performance analysis on a function and applying optimization with regression tests
Security hygiene improvements by removing hard-coded credentials and upgrading dependencies, plus checks
Implementing a CI quality gate that fails on missing tests or lint errors

Frequently Asked Questions

Add this skill to your agents