Skip to content
Back to skills

Code Quality Workflow

ASecurity

Mandatory code quality workflow that must run after ANY code changes. Use after creating/editing files, before commits, or when fixing errors. Keywords - testing, linting, formatting, typecheck, quality gates, workflow.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
testingtypescriptshelltestingdebuggingapidocumentation

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill code-quality-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Quality Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Quality Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-code-quality-workflow/badge)](https://www.skillsdirectory.com/skills/david-li0406-code-quality-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-quality-workflow
description: Mandatory code quality workflow that must run after ANY code changes. Use after creating/editing files, before commits, or when fixing errors. Keywords - testing, linting, formatting, typecheck, quality gates, workflow.
license: MIT
metadata:
  version: "2.0.0"
  author: jpmorgan-payments
  lastUpdated: "2025-12-24"
  priority: critical
---

# Code Quality Workflow

Mandatory code quality workflow ensuring all code meets standards before commits. This workflow runs automated type checking, formatting, linting, and testing.

## When to Apply

Use this workflow:
- After making ANY code changes
- Before committing code
- When fixing errors or issues
- During code review preparation

## ⚠️ CRITICAL: Mandatory Steps

**After making ANY code changes, you MUST:**

1. **Format code**: `cd embedded-components; yarn format`
2. **Run tests**: `cd embedded-components; yarn test`
3. **Fix any errors that appear**
4. **Re-run tests until all pass**

## Quick Reference

### The Test Command

```powershell
cd embedded-components
yarn test
```

This runs in sequence:
1. `typecheck` - TypeScript type checking
2. `format:check` - Prettier formatting verification
3. `lint` - ESLint linting
4. `test:unit` - Vitest unit tests

### Quick Fix Commands

```powershell
cd embedded-components

# Auto-fix formatting
yarn format

# Auto-fix linting
yarn lint:fix

# Check types only
yarn typecheck

# Run tests only
yarn test:unit

# Full test suite
yarn test
```

## Never Commit Code With

- ❌ TypeScript errors
- ❌ Formatting errors (Prettier)
- ❌ Linting errors
- ❌ Failing tests

## Coverage Requirements

- ✅ Minimum 80% line coverage
- ✅ All new code must have tests
- ✅ Tests must be colocated with implementation
- ✅ Use MSW for API mocking

## How to Use

For detailed instructions, examples, and troubleshooting:

- **Full guide**: `AGENTS.md` - Complete workflow documentation
- **Related skills**: 
  - `test-and-fix-workflow` - Systematic debugging workflow
  - `component-testing` - Testing patterns and examples

## References

- See `embedded-components/package.json` for all scripts
- See `AGENTS.md` for complete workflow documentation
- See `embedded-components/CONTRIBUTING.md` for contribution guidelines

Files in this skill

  • AGENTS.md6 KB
  • SKILL.md2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…