本文へ移動
cccskills
無料GitHub で公開

lint

Detect the project's linters and formatters, run them, and fix every error. Use when asked to lint or clean up style and type errors.

日本語の概要は準備中です。原文の説明を表示しています。

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Lint — Lint, Format & Type Check

You are a code quality engineer. Auto-detect the linting stack, run it, fix all errors. Zero errors before done.

Do NOT ask for permission — just fix everything.


Step 1 — Detect lint stack

PROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
ls pyproject.toml ruff.toml eslint.config.* .eslintrc* tsconfig.json 2>/dev/null
ls api/eslint.config.* api/.eslintrc* api/tsconfig.json 2>/dev/null

Determine which apply:

  • ruff (Python): pyproject.toml with [tool.ruff] section
  • ESLint (frontend): eslint.config.* or .eslintrc* in root
  • ESLint (backend JS): eslint.config.* or .eslintrc* in api/
  • TypeScript (frontend): tsconfig.json in root
  • TypeScript (backend): tsconfig.json in api/

Step 2 — Auto-fix

ruff (Python):

./venv/bin/ruff check . --fix
./venv/bin/ruff format .

ESLint (frontend):

npm run lint -- --fix 2>/dev/null || npx eslint . --fix

ESLint (backend JS):

cd api && npm run lint -- --fix 2>/dev/null || npx eslint src --ext .ts --fix

Step 3 — Type check

TypeScript (frontend) — blocking:

npm run typecheck 2>&1 || npx tsc --noEmit 2>&1

TypeScript (backend JS) — blocking:

cd api && npm run typecheck 2>&1 || npx tsc --noEmit 2>&1

Python mypy — non-blocking:

./venv/bin/mypy . --ignore-missing-imports 2>&1 || true

Step 4 — Fix remaining errors manually

For each error auto-fix could not handle, read the file and fix it.

ESLint:

  • no-unused-vars / @typescript-eslint/no-unused-vars → remove or prefix with _
  • @typescript-eslint/no-explicit-any → replace with proper type or unknown
  • no-console → replace with project logger
  • react-hooks/exhaustive-deps → add missing deps or wrap with useCallback/useMemo
  • @typescript-eslint/no-non-null-assertion → add null check instead of !

TypeScript:

  • TS2339 (property does not exist) → add to type or use optional chaining
  • TS2345 (type mismatch) → fix type or cast with justification
  • TS2304 (cannot find name) → add import
  • TS7006 (implicit any) → add explicit type annotation

ruff:

  • E501 (line too long) → break the line
  • B904 (raise from) → add from err or from None
  • F841 (unused variable) → remove it
  • C408 (unnecessary dict call) → use dict literal

Step 5 — Re-run until clean

Run each applicable command again. Repeat Steps 4-5 until zero errors.

# ruff
./venv/bin/ruff check .
./venv/bin/ruff format --check .

# ESLint + TypeScript
npm run lint && npm run typecheck
cd api && npm run lint

Output

=== Lint Summary ===
Frontend ESLint:    X errors → 0 remaining
Frontend TypeCheck: X errors → 0 remaining
Backend ESLint:     X errors → 0 remaining
Backend TypeCheck:  X errors → 0 remaining
ruff:               X errors → 0 remaining
Status:             PASSED

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

ai-seo

無料

When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

architect

無料

Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

rajitsaha のスキルをすべて見る

このスキルの問題を報告する