Skip to content
Back to skills

Frontend Debug Linting

ASecurity

Quality gates for frontend code. ALWAYS use after writing React/Next.js code and before delivery. Covers: ESLint linting, TypeScript type-checking, Prettier formatting, browser console debugging. Catches errors before they reach users.

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 8, 2026
developmenttypescriptbashreactnextjsdebuggingfrontend

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill frontend-debug-linting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Frontend Debug Linting?

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

Security grade badge for Frontend Debug Linting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-frontend-debug-linting/badge)](https://www.skillsdirectory.com/skills/majiayu000-frontend-debug-linting)

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: frontend-debug-linting
description: Quality gates for frontend code. ALWAYS use after writing React/Next.js code and before delivery. Covers: ESLint linting, TypeScript type-checking, Prettier formatting, browser console debugging. Catches errors before they reach users.
allowed-tools: Read, Edit, Bash (*)
---

# Debug & Linting

Catch errors before delivery. Lint, type-check, browser verify.

## When to Use

- After writing code → run checks
- Before delivery → verify quality
- Debugging → check console/network

## Process

**LINT → TYPE → BROWSER → DELIVER**

1. Run lint: `npm run lint`
2. Type check: `npm run typecheck`
3. Browser check: console + screenshot
4. Deliver when clean

## Quick Commands

```bash
npm run lint          # ESLint check
npm run lint:fix      # Auto-fix
npm run typecheck     # TypeScript check
npm run format        # Prettier format
npm run check         # All checks
```

## Common Fixes

### TypeScript

```yaml
"Type 'X' not assignable to 'Y'":
  → Fix type mismatch or add assertion

"'X' declared but never used":
  → Remove or prefix with _

"Object possibly 'undefined'":
  → Add null check: obj?.property
  → Add fallback: obj ?? default
```

### React

```yaml
"Missing dependencies in useEffect":
  → Add deps or wrap in useCallback

"Each child should have unique key":
  → Add key={item.id} to list items

"img must have alt prop":
  → Add alt text or alt=""
```

### Formatting

```yaml
"Prettier errors":
  → Run: npm run format
```

## Browser Verification

```yaml
# Check console errors
browser_console_messages: { onlyErrors: true }
→ Must be empty before delivery

# Check network
browser_network_requests
→ No failed (4xx, 5xx) requests

# Debug element styles
browser_evaluate: { function: "() => getComputedStyle(el)" }
```

## Pre-Delivery Checklist

```yaml
MUST PASS:
  - [ ] npm run lint → 0 errors
  - [ ] npm run typecheck → 0 errors
  - [ ] browser_console_messages → 0 errors
  - [ ] No failed network requests

CAN DELIVER WITH:
  - ESLint warnings (with explanation)
  - Console warnings (if understood)
```

## Project Setup

```bash
# Add to existing Next.js project
npm install -D prettier eslint-config-prettier

# package.json scripts
{
  "lint": "eslint . --ext .ts,.tsx",
  "lint:fix": "eslint . --ext .ts,.tsx --fix",
  "format": "prettier --write .",
  "typecheck": "tsc --noEmit",
  "check": "npm run typecheck && npm run lint"
}
```

## Debug Checklist

```yaml
WHEN SOMETHING BREAKS:
  1. browser_console_messages → check errors
  2. browser_network_requests → failed requests?
  3. npm run typecheck → type errors?
  4. Add console.log → trace flow
  5. Isolate → comment out sections
  6. Fix → run checks → verify
```

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.