메뉴
Use this skill when the user says "run lint", "fix lint errors", "ruff check", "lint my code", or when ruff violations appear in build output. Triggers include: "make lint", "ruff check", "linting errors", "format code". When in doubt, use this skill rather than skipping it.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill when the user says "import data", "bulk insert", "load cases", "add tips from file", "seed database", or wants to import cases/tips from JSON/CSV files. Triggers include: "import cases", "bulk load", "database seeding", "json to database", "csv import", "load test data". When in doubt, use this skill rather than skipping it.
Use this skill when the user says "docker compose not working", "container won't start", "database connection failed", "Docker health check failing", or when `make docker-up` fails. Triggers include: "docker error", "container unhealthy", "pgvector not loading", "env var missing in container", "docker logs error". When in doubt, use this skill rather than skipping it.
Use this skill when the user says "check system health", "verify services", "diagnose issues", "is everything running", or wants a comprehensive system status report. Triggers include: "health check", "system status", "verify setup", "diagnostic report", "what's broken", "check connectivity". When in doubt, use this skill rather than skipping it.
Use this skill when the user says "create endpoint", "add API route", "new API", "add endpoint", "create API", or wants to add a new REST endpoint to the project. Triggers include: "add /api/v1/xxx endpoint", "create new route", "new FastAPI endpoint". When in doubt, use this skill rather than skipping it.
Use this skill when the user says "run tests", "pytest", "test failing", "make test", "run the test suite", or when test output shows failures. Triggers include: "make test", "pytest tests/", "test error", "test coverage", "test_api", "test-services". When in doubt, use this skill rather than skipping it.
Use this skill when the user says "debug retrieval", "check RRF", "fix search", "analyze search results", "BM25 not working", "vector search broken", or when the /api/v1/analyze endpoint returns unexpected results. Triggers include: "retrieval issue", "hybrid search not working", "RRF fusion error", "search returning wrong results", "embedding mismatch". When in doubt, use this skill rather than skipping it.
| name | ruff-lint-fixer |
| description | Use this skill when the user says "run lint", "fix lint errors", "ruff check", "lint my code", or when ruff violations appear in build output. Triggers include: "make lint", "ruff check", "linting errors", "format code". When in doubt, use this skill rather than skipping it. |
| license | MIT |
| metadata | {"version":"1.0.0","author":"Repository Analyst","priority":"high","category":"code-quality"} |
You are an expert in Python code quality using ruff linter. Your job is to run ruff check, analyze violations, and apply targeted fixes following the project's linting conventions.
make lint to identify all ruff violations.make fmt to apply auto-fixes for fixable issues (unused imports, formatting, etc.).make lint again to confirm all issues are resolved.pyproject.toml)ruff check .ruff format . && ruff check --fix .app/ or tests/ directories without explicit confirmation.--fix blindly — verify each change makes sense in context.make lint fails 3 times consecutively after fixes, STOP and report the specific errors.make lint after make fmt to ensure no regressions.User: "Run lint and fix any issues"
Assistant:
Thinking:
make lint to see all violations.make fmt to auto-fix formatting and fixable issues.make lint to check remaining errors.Uses the bash tool with command make lint
Uses the bash tool with command make fmt