61-validate-lint-150

[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.

16 stars

Best use case

61-validate-lint-150 is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.

Teams using 61-validate-lint-150 should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/61-validate-lint-150/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/61-validate-lint-150/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/61-validate-lint-150/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How 61-validate-lint-150 Compares

Feature / Agent61-validate-lint-150Standard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Validate-Lint 150 Protocol

**Core Principle:** Code quality is non-negotiable. Run comprehensive checks before any delivery. Catch issues early, fix systematically.

## What This Skill Does

When you invoke this skill, you're asking AI to:
- **Run full lint suite** — ESLint + TypeScript + Unused code detection
- **Report all issues** — Categorized by severity and type
- **Provide fix guidance** — Specific suggestions for each error
- **Verify resolution** — Re-run checks after fixes
- **Quality gate** — Only proceed when all checks pass

## The 150% Lint Rule

| Dimension | 100% Core | +50% Enhancement |
|-----------|-----------|------------------|
| **ESLint** | No lint errors | + Consistent code style |
| **TypeScript** | Compiles cleanly | + Strict type checking |
| **Unused Code** | No unused locals | + Clean imports/exports |
| **Standards** | Follows rules | + Project conventions |

## Quality Check Framework

```
LINT INTEGRITY CHECK (100% Required)
├── ESLint Rules: No violations (style, logic, best practices)
├── TypeScript: Clean compilation, no type errors
├── Unused Code: No unused locals (parameters allowed for interfaces)
└── Import Hygiene: Clean, organized imports

ENHANCED VALIDATION (50% Enhancement)
├── Code Standards: Follows project conventions
├── Complexity: Cognitive complexity within limits
├── Consistency: Matches codebase patterns
└── Future-Proofing: No deprecated patterns
```

## Command Execution

from `my-preacher-helper/`
```bash
npm run lint:full
```

This runs three sequential checks:
1. `npm run lint` — ESLint code quality rules
2. `npm run compile` — TypeScript compilation check
3. `npm run lint:unused` — Unused code detection

## Error Classification

| Error Type | Severity | Action Required |
|------------|----------|----------------|
| **ESLint Error** | High | Must fix before commit |
| **TypeScript Error** | Critical | Blocks compilation |
| **Unused Local** | Medium | Remove or prefix with `_` |
| **Import Issues** | Medium | Clean up imports |

## Common Fix Patterns

### ESLint Fixes
```bash
# Auto-fix what can be auto-fixed
npm run lint -- --fix

# Manual fixes for complex issues
# - Add missing JSDoc
# - Fix import order
# - Remove duplicate code
```

### TypeScript Fixes
```typescript
// Fix common type errors
// 1. Add missing type annotations
// 2. Import missing types
// 3. Fix property access on union types
// 4. Add null/undefined checks
```

### Unused Code Fixes
```typescript
// For intentionally unused parameters (interfaces)
function handler(_unused: string) { /* ... */ }

// For temporarily unused locals
// eslint-disable-next-line @typescript-eslint/no-unused-vars
const tempVar = 'remove later';
```

## Execution Protocol

### Phase 1: Initial Check
```bash
npm run lint:full
```
- Capture all errors
- Categorize by type
- Prioritize critical issues

### Phase 2: Fix Cycle
```
For each error category:
├── Fix critical TypeScript errors first
├── Fix ESLint errors next
├── Clean unused code last
└── Re-run checks after each category
```

### Phase 3: Verification
```bash
npm run lint:full
```
- Confirm all issues resolved
- Document any intentional deviations
- Ready for commit/integration

## Success Criteria

- **All TypeScript errors resolved** (compilation clean)
- **Zero ESLint violations** (or documented exceptions)
- **No unused locals** (unused parameters allowed for interfaces)
- **Clean build** (no warnings that break standards)

## Failure Recovery

| Failure Mode | Detection | Recovery |
|--------------|-----------|----------|
| **Auto-fix breaks logic** | Tests fail after --fix | Revert auto-fixes, manual repair |
| **TypeScript strictness** | Overly complex type fixes | Use `any` with TODO comment |
| **Unused but needed** | Removal breaks functionality | Add `_` prefix or eslint-disable |
| **Import cycles** | Complex dependency issues | Restructure imports or use barrels |

## Integration Points

- **Pre-commit hooks** — Run automatically before commits
- **CI/CD pipeline** — Quality gate in deployment
- **Code review** — Manual verification of complex fixes
- **Refactoring** — Clean up after major changes

## Quality Metrics

| Metric | Target | Current Status |
|--------|--------|----------------|
| **ESLint Violations** | 0 | Check required |
| **TypeScript Errors** | 0 | Check required |
| **Unused Code** | 0 locals | Check required |
| **Build Success** | 100% | Must pass |

---

**Lint 150 ensures code quality standards are maintained at the highest level, preventing technical debt and maintaining codebase health.**

Related Skills

validate-historical

16
from diegosouzapw/awesome-omni-skill

Validate historical data completeness and quality over date ranges

Validate with Database

16
from diegosouzapw/awesome-omni-skill

Connect to live PostgreSQL database to validate schema assumptions, compare pg_dump vs pgschema output, and query system catalogs interactively

lint-and-validate

16
from diegosouzapw/awesome-omni-skill

Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.

lint-and-format

16
from diegosouzapw/awesome-omni-skill

Runs linting and formatting checks before committing. Use this skill after writing or modifying code to ensure it passes all linters and formatters before creating a commit.

api-validate

16
from diegosouzapw/awesome-omni-skill

API contract validation and breaking change detection

validate-agent-files

16
from diegosouzapw/awesome-omni-skill

Validates AI coding assistant customization files (agents, skills, prompts, instructions) for correct format and structure. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use when checking if agent files are properly configured, troubleshooting agent issues, or before committing new customization files.

chatgpt-app:validate

16
from diegosouzapw/awesome-omni-skill

Run validation suite on your ChatGPT App to check schemas, annotations, widgets, and UX compliance.

agent-validate-config

16
from diegosouzapw/awesome-omni-skill

Validate agent YAML frontmatter and configuration. Use before committing agent changes or in CI.

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

absinthe-subscriptions

16
from diegosouzapw/awesome-omni-skill

Use when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.

absinthe-resolvers

16
from diegosouzapw/awesome-omni-skill

Use when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling.

abramov-state-composition

16
from diegosouzapw/awesome-omni-skill

Write JavaScript code in the style of Dan Abramov, co-creator of Redux and React core team member. Emphasizes predictable state management, composition over inheritance, and developer experience. Use when building React applications or managing complex state.