Code Quality Excellence Skill

Purpose

Maintain high code quality through automated static analysis, TypeScript strict mode, and quality gates for MCP server projects.

When to Use

• ✅ Before committing TypeScript code
• ✅ In CI/CD pipeline quality checks
• ✅ During code reviews
• ✅ Regular quality audits

TypeScript Strict Mode

{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "noUncheckedIndexedAccess": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "exactOptionalPropertyTypes": true
  }
}

ESLint Configuration

// eslint.config.js
import tseslint from 'typescript-eslint';

export default tseslint.config(
  tseslint.configs.strictTypeChecked,
  {
    rules: {
      '@typescript-eslint/no-explicit-any': 'error',
      '@typescript-eslint/prefer-nullish-coalescing': 'error',
      '@typescript-eslint/strict-boolean-expressions': 'error',
      '@typescript-eslint/explicit-function-return-type': 'error',
    }
  }
);

Quality Gates

Quality Commands

npm run lint          # ESLint check
npx tsc --noEmit      # Type checking
npm run knip          # Unused detection
npm test              # Unit tests
npm run test:coverage # Coverage report
npm run test:licenses # License compliance

ISMS Policy References

Core policies:

• Secure Development Policy — Primary: Code-quality gates are mandatory SDLC controls; TypeScript strict + ESLint + tests + SAST
• Open Source Policy — Licence compliance (allowlist), npm run test:licenses, SBOM
• Information Security Policy — Quality as a risk-reduction control and transparency enabler

Supporting policies:

• Change Management — Gates run on every PR before merge
• Vulnerability Management — Lint / CodeQL findings triaged with CVSS where applicable
• AI Policy — AI-generated code must pass the same quality gates as human code